ork on
> it, but
> I can help in free hours)
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Griggs, Donald
> Sent: segunda-feira, 12 de maio de 2008 10:47
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite]
> it, but
> I can help in free hours)
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Griggs, Donald
> Sent: segunda-feira, 12 de maio de 2008 10:47
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Di
ROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Griggs, Donald
Sent: segunda-feira, 12 de maio de 2008 10:47
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Distributed transaction best practices
Hi David,
Regarding: "What are the recommended "best practices" around
Hi David,
Regarding: "What are the recommended "best practices" around using
SQLite in a distributed scenario?" [two-phase commit, etc.]
I trust that someone with some actual relevant knowledge will reply to
your query later, but I imagine that many would say the the "recommend
best practice"
What are the recommended "best practices" around using SQLite in a
distributed scenario?
(I saw Shailesh's email in March; I'm considering building a two-phase
commit layer atop SQLite nodes and looking for advice.)
Clearly, this is a big topic including failover, recovery,
load-balancing, and
5 matches
Mail list logo