[sqlite] 1-way replication best practices?

2007-09-27 Thread Cyrus Durgin
hi, i'm using sqlite3 in a small project that will run on multiple servers. only one of the instances will be read-write to the database, the others are all read-only. i understand that the recommended process for replication on the read-write instance looks something like: BEGIN EXCLUSIVE; COM

Re: [sqlite] 1-way replication best practices?

2007-09-27 Thread Dan Kennedy
On Thu, 2007-09-27 at 14:26 -0700, Cyrus Durgin wrote: > hi, > > i'm using sqlite3 in a small project that will run on multiple servers. > only one of the instances will be read-write to the database, the others are > all read-only. i understand that the recommended process for replication on > t

Re: [sqlite] 1-way replication best practices?

2007-09-27 Thread Cyrus Durgin
hey dan, thanks, that's what i was expecting (but hoping wasn't the case :) i'm using ruby on rails for the app, so hopefully it will only hold connections to the db open long enough for each request? can anyone confirm this is true? if i just have to wait for existing connections to die off th

Re: [sqlite] 1-way replication best practices?

2007-09-28 Thread John Stanton
way. Nikola Miljkovic wrote: [In the message "Re: [sqlite] 1-way replication best practices?" on Sep 28, 11:29, Dan Kennedy writes:] On Thu, 2007-09-27 at 14:26 -0700, Cyrus Durgin wrote: hi, i'm using sqlite3 in a small project that will run on multiple servers. only one o

Re: [sqlite] 1-way replication best practices?

2007-09-28 Thread Nikola Miljkovic
[In the message "Re: [sqlite] 1-way replication best practices?" on Sep 28, 11:29, Dan Kennedy writes:] > On Thu, 2007-09-27 at 14:26 -0700, Cyrus Durgin wrote: > > hi, > > > > i'm using sqlite3 in a small project that will run on multiple servers. > &