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
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
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
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
[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.
> &
5 matches
Mail list logo