RE: how issue-2897 branch solves reflective merges?

Hi Justin,

-----Original Message-----
From: justin.erenkrantz_at_gmail.com on behalf of Justin Erenkrantz
Sent: Fri 1/11/2008 10:09 PM
To: Kamesh Jayachandran

>I'm not in favor of having SQLite as a dependency if at all possible,
>so let me rephrase the question:

Me too does not like it.
Just for your info we use sqlite for node-origins cache, So as a dependency it would still remain.

>While the current implementation obviously uses SQLite, are the
>algorithms used dependent upon relational features only present in
>SQL? If not, then can we rewrite the algorithms using a flat-file
>index or something similar?

Algorithms that does this reflective merge is purely client side and hence no interaction directly with sqlite.

>I'm not suggesting that you have to do that work before it gets merged
>to trunk, but I guess a number of us (hi dglasser) would like to
>remove SQLite if we can.

Yes I also would like to start working on it after this code finds its place in /trunk.

With regards
Kamesh Jayachandran
Received on 2008-01-11 20:10:23 CET