On 2/9/2011 7:42 PM, Sam Carleton wrote:
> Currently I have two and sometimes three clients access the SQLite db, all
> on the same machine.
>
> * A C# program that doesn't ever stay connection all that long.
> * An Apache application that stays connected all the time.
> * A Qt application that sta
On Wed, Feb 9, 2011 at 6:35 PM, Sam Carleton wrote:
> Ok, the question now is if I should stop the slow walk towards a
> client/server DB and start running...
>
I'm guessing that if you enable WAL you will get all the concurrency you
need and then some.
--
D. Richard Hipp
d...@sqlite.org
__
On Wed, Feb 9, 2011 at 1:46 PM, Igor Tandetnik wrote:
>
> On 2/9/2011 1:42 PM, Sam Carleton wrote:
>
> > It is my understanding that SQLite is designed to allow multiple clients
> > from the same computer to access the DB file at one time.
>
> Yes. But if one of those clients starts to write, othe
On 2/9/2011 1:42 PM, Sam Carleton wrote:
> Currently I have two and sometimes three clients access the SQLite db, all
> on the same machine.
>
> * A C# program that doesn't ever stay connection all that long.
> * An Apache application that stays connected all the time.
> * A Qt application that sta
Currently I have two and sometimes three clients access the SQLite db, all
on the same machine.
* A C# program that doesn't ever stay connection all that long.
* An Apache application that stays connected all the time.
* A Qt application that stays connected when it is running.
I am getting repor
5 matches
Mail list logo