From: Andreas Ericsson Date: Tue, 04 Sep 2007 16:51:34 GMT Subject: Re: Git's database structure Message-ID: <46DD8D16.9090104@op5.se> In-Reply-To: <9e4733910709040947ia32bda4i6e30efb2d7848308@mail.gmail.com> Jon Smirl wrote: > On 9/4/07, Andreas Ericsson wrote: >> Jon Smirl wrote: >>> Another way of looking at the problem, >>> >>> Let's build a full-text index for git. You put a string into the index >>> and it returns the SHAs of all the file nodes that contain the string. >>> How do I recover the path names of these SHAs? >>> >> I wouldn't know, but presumably any table can have more than one column. >> >> Is this a problem you face with git so often that it requires a complete >> re-design of its very core? > > That's the whole point. We need to discuss the impact of merging a > field (path names) with an index (tree nodes) has on future things we > may want to do with the data stored in git. > Yes, but as nobody seems to know what those future things are, it feels rather pointless speculating about adding support to git for them. git is a tool. It's a great one at that, because it was built to solve a particular problem, which it does an amazing job at. Other SCM's which had the potential to become amazingly good tools too drowned somewhere between prototype and product in a sea of intellectual masturbation, which had little to do with solving real-world problems. -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231