[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: My understanding of state of things on sqlite storage

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 24 Jan 2008 10:11:34 -0500

On Jan 24, 2008 10:09 AM, David Glasser <glasser_at_davidglasser.net> wrote:
> On Jan 24, 2008 6:40 AM, Kamesh Jayachandran <kamesh_at_collab.net> wrote:
> > C. Michael Pilato wrote:
> > > Kamesh Jayachandran wrote:
> > >> With this I tend to think we need to do 3 things,
> > >>
> > >> 1)In trunk Make 'get_mergeinfo_for_tree' API to be sqlite independent.
> > >>
> > >> 2)In issue-2897 branch make 'get_commit_and_merge_ranges' extract
> > >> data from fs rather than from sqlite.
> > >
> > > 2b) Implement all the other mergeinfo queries for BDB, too.
> >
> > Thanks for clarifying that, I am working on implementing 2) right now.
>
> That's good to hear. What is your design for doing this efficiently?
>
> The design I've been imagining involves adding a field to noderevs
> "predecessor-where-mergeinfo-changed" or something.

Ahhh! So you have not made that change yet I take it? Or only for
fsfs? I was thinking this was part of the reintegrate branch which is
also why I thought the SQLite usage had all been removed. Maybe you
only did it for fsfs?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-24 16:11:44 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.