Re: My understanding of state of things on sqlite storage
David Glasser 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.
/me sighs as the beautiful design of the filesystem DAG crumbles into a
giant mess, basically all because of one feature's supposed need for
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-01-24 16:47:10 CET
This is an archived mail posted to the Subversion Dev