Alex, I've looked at your code and discussions on this list about the versioning. I have a few questions.
1. How are you moving the data around from one master to another? 2. How are you applying the changes once moved to the master? --- On Fri, 7/31/09, Alexey Pechnikov <pechni...@mobigroup.ru> wrote: > From: Alexey Pechnikov <pechni...@mobigroup.ru> > Subject: Re: [sqlite] Multi-master replication with updated Versioning > extension > To: sqlite-users@sqlite.org > Cc: "D. Richard Hipp" <d...@hwaci.com> > Date: Friday, July 31, 2009, 8:42 AM > Hello! > > I made some changes: > hash field in actions table has always > name "checksum" (so versioning and replication logic doesn't > influence of hash algorithm) > versioning() function without second > argument now start "local" mode > history and actions tables are renamed > > Updated files is here > http://mobigroup.ru/files/sqlite-ext/versioning/ > > Now there are two problems in the realization: > the "replace" conflict resolution algorithm > for SOURCE table may produce errors - tickets 3964, 3982 > versioning_drop() function doesn't work - > ticket 4001 > > Best regards, Alexey Pechnikov. > http://pechnikov.tel/ > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
