Kelly, The "journal" file for sqlite is not a redo journal but rather an undo journal. So it is not really possible to use the journal to replicate.
However, if one were to hack the code and open a redo file along with the journal file. Then write the source blocks out as well. This could then be copied and written against a target database on a remote server. Ultimately this would be what rsync provides without the rescans... You could also look into some form of filesystem replication as well. I think that would be more reliable. Just my .02 hth, ken --- On Sat, 7/18/09, Kelly Jones <[email protected]> wrote: > From: Kelly Jones <[email protected]> > Subject: [sqlite] SQLite3 replication > To: [email protected] > Date: Saturday, July 18, 2009, 12:18 PM > Is there any way to real-time > replicate SQLite3 dbs across servers? > > I realize I could just rsync constantly, but this seems > inefficient. > > I know SQLite3 uses a journal when making changes: could I > use this > journal for replication, similar to how MySQL uses > bin-logging for > replication? > > -- > We're just a Bunch Of Regular Guys, a collective group > that's trying > to understand and assimilate technology. We feel that > resistance to > new ideas and technology is unwise and ultimately futile. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
