Re: [sqlite] Multi-master replication with updated Versioning extension

Hello! On Friday 31 July 2009 18:34:17 Ken wrote: > 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? By the

Re: [sqlite] Multi-master replication with updated Versioning extension

hni...@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, 2

Re: [sqlite] Multi-master replication with updated Versioning extension

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

Re: [sqlite] Multi-master replication with updated Versioning?extension

On 30 Jul 2009, at 6:19pm, Jay A. Kreibich wrote: > You're not really supposed to > dump and restore a multi-master system. We're back to talking about synchronising different copies of the database again, aren't we ? Dumping and restoring a multi-master system means restoring the entire

Re: [sqlite] Multi-master replication with updated Versioning?extension

On Thu, Jul 30, 2009 at 08:33:10PM +0400, Alexey Pechnikov scratched on the wall: > Hello! > > On Thursday 30 July 2009 19:47:39 Jay A. Kreibich wrote: > > Then again, given that ROWID values are signed 64 bit values, you > > could just start each master at some offset (like

Re: [sqlite] Multi-master replication with updated Versioning extension

On Thu, Jul 30, 2009 at 06:11:42PM +0400, Alexey Pechnikov scratched on the wall: > Hello! > > On Thursday 30 July 2009 17:25:15 P Kishor wrote: > > > I haven't looked at your work in depth, but I am interested in this. I > > > have implemented a very simple versioning system with TRIGGERs

Re: [sqlite] Multi-master replication with updated Versioning extension

009 7:11 AM Subject: Re: [sqlite] Multi-master replication with updated Versioning extension > Hello! > > On Thursday 30 July 2009 17:25:15 P Kishor wrote: >> > I haven't looked at your work in depth, but I am interested in >> > this. I >> > have implemented a

Re: [sqlite] Multi-master replication with updated Versioning extension

Hello! On Thursday 30 July 2009 17:25:15 P Kishor wrote: > > I haven't looked at your work in depth, but I am interested in this. I > > have implemented a very simple versioning system with TRIGGERs whereby > > every change (INSERT, UPDATE, DELETE) in a column in a table is stored > > in a

Re: [sqlite] Multi-master replication with updated Versioning extension

On Thu, Jul 30, 2009 at 7:42 AM, P Kishor wrote: > Alexey, > > > On Thu, Jul 30, 2009 at 4:42 AM, Alexey Pechnikov > wrote: >> Hello! >> >> Please see >> http://mobigroup.ru/files/sqlite-ext/versioning/ > > I haven't looked at your work in depth, but I

Re: [sqlite] Multi-master replication with updated Versioning extension

Alexey, On Thu, Jul 30, 2009 at 4:42 AM, Alexey Pechnikov wrote: > Hello! > > Please see > http://mobigroup.ru/files/sqlite-ext/versioning/ I haven't looked at your work in depth, but I am interested in this. I have implemented a very simple versioning system with

[sqlite] Multi-master replication with updated Versioning extension

Hello! Please see http://mobigroup.ru/files/sqlite-ext/versioning/ Master-slave may use ROWIDs and multy-master may use md5 hash of full record. This is test version and I'm glad to get any comments and ideas. P.S. md5 extension sources is here http://mobigroup.ru/files/sqlite-ext/md5/ Best