Blair Zajac wrote:
> Malcolm Rowe wrote:
> > The current mergeinfo backend creates a SQLite database called
> > 'mergeinfo.db'. However, as I understand it, it's not the canonical
> > source for mergeinfo (that's the properties on the noderevs).
> > mergeinfo.db is just an index, and could (and probably should, for
other
> > reasons) be regenerated by e.g. svnadmin recover.
> >
> > Secondly, I wonder what we'll do when we want to add more derived
> > information to the filesystem (e.g. someone [I forget who, sorry]
showed
> > a proof-of-concept SQLite property indexer a while back). Will we
> > create another SQLite database?
> >
> > So, I propose we rename mergeinfo.db to something more generic: say,
> > indexes.db. You can all lynch me now.
>
> Should we also rename it to indexes.sqlite to make the name specific
to
> the
> database we're using?
I don't think you gain anything by naming the bike for the wrench you
plan to use on it. I think "indexes.db" or "index.db" would be fine.
-Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 19 19:53:20 2007