git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: "Jon Smirl" <jonsmirl@gmail.com>, "Andreas Ericsson" <ae@op5.se>,
	"Theodore Tso" <tytso@mit.edu>,
	"Junio C Hamano" <gitster@pobox.com>
Subject: Re: Git's database structure
Date: Wed, 5 Sep 2007 20:52:06 +0100	[thread overview]
Message-ID: <200709052052.07597.andyparkins@gmail.com> (raw)
In-Reply-To: <9e4733910709050641j34d58683ra72caa52c56cdf0f@mail.gmail.com>

On Wednesday 2007, September 05, Jon Smirl wrote:

> The path name field needs to be moved back into the blobs to support
> alternative indexes. For example I want an index on the Signed-off-by
> field. I use this index to give me the SHAs for the blobs
> Signed-off-by a particular person. In the current design I have no way
> of recovering the path name for these blobs other than a brute force
> search following every path looking for the right SHA.

Erm, if that's your only way then you designed your index incorrectly.

 1. Signed-Off-By lines appear in commits, so your index should be an index
    of SOB name against commit hash
 2. Lookup the commit for that commit hash.  As usual this is blindlingly
    git-fastic.
 3. That commit blob contains a tree hash.  Look it up.  As usual this is 
    blindingly git-fastic
 4. Start gathering blobs for that tree.  Fast, fast, fast.
 5. Any subtree objects you come across, goto 4.

This is not a brute force lookup and it's stuff that git is really good at 
anyway.

I'm really not sure I see what problem you're trying to solve.  Whatever 
index you want, you could keep and maintain if you wanted to without 
impacting git's core storage at all.



Andy

-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

  parent reply	other threads:[~2007-09-05 19:52 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 15:23 Git's database structure Jon Smirl
2007-09-04 15:55 ` Andreas Ericsson
2007-09-04 16:07   ` Mike Hommey
2007-09-04 16:10     ` Andreas Ericsson
2007-09-04 16:19   ` Jon Smirl
2007-09-04 16:29     ` Andreas Ericsson
2007-09-04 17:09     ` Jeff King
2007-09-04 20:17     ` David Tweed
2007-09-04 17:21   ` Junio C Hamano
2007-09-04 16:28 ` Jon Smirl
2007-09-04 16:31   ` Andreas Ericsson
2007-09-04 16:47     ` Jon Smirl
2007-09-04 16:51       ` Andreas Ericsson
2007-09-04 17:25   ` Junio C Hamano
2007-09-04 17:44     ` Jon Smirl
2007-09-04 18:04       ` Mike Hommey
2007-09-04 19:44         ` Reece Dunn
2007-09-04 18:06       ` Junio C Hamano
2007-09-04 21:25       ` Theodore Tso
2007-09-04 21:54         ` Jon Smirl
2007-09-05  7:18           ` Andreas Ericsson
2007-09-05 13:41             ` Jon Smirl
2007-09-05 14:51               ` Andreas Ericsson
2007-09-05 15:37                 ` Jon Smirl
2007-09-05 15:54                   ` Julian Phillips
2007-09-05 16:12                     ` Jon Smirl
2007-09-05 17:31                       ` Julian Phillips
2007-09-06  1:27                         ` Kyle Moffett
2007-09-05 17:39                       ` Mike Hommey
2007-09-06  8:49                       ` Andreas Ericsson
2007-09-06  9:09                         ` Junio C Hamano
2007-09-06 11:03                           ` Wincent Colaiuta
2007-09-06 12:56                       ` Johannes Schindelin
2007-09-06 18:14                         ` Steven Grimm
2007-09-07  0:33                       ` Martin Langhoff
2007-09-05 19:52               ` Andy Parkins [this message]
2007-09-04 17:19 ` Julian Phillips
2007-09-04 17:30   ` Jon Smirl
2007-09-04 18:51     ` Andreas Ericsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200709052052.07597.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonsmirl@gmail.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).