Re: [sqlite] Sqlite concurrency problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Clarke wrote: > So one can share one open raw database connection across multiple threads can > you? That is true in theory but there are some issues in practise. For example there is currently no thread safe way to get error messages (being ad

Re: [sqlite] Sqlite concurrency problem

: Re: [sqlite] Sqlite concurrency problem On Nov 3, 2008, at 8:04 AM, Paul Clarke wrote: > Is it really correct that in order to perform an INSERT, Sqlite > demands > that no other connections be active? > > It uses the same database instance but (obviously) separate statem

Re: [sqlite] Sqlite concurrency problem

On Nov 3, 2008, at 8:04 AM, Paul Clarke wrote: > Is it really correct that in order to perform an INSERT, Sqlite > demands > that no other connections be active? > > It uses the same database instance but (obviously) separate statements > for each operation > Please distinguish between a "conn

Re: [sqlite] Sqlite concurrency problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Clarke wrote: > Is it really correct that in order to perform an INSERT, Sqlite demands > that no other connections be active? http://www.sqlite.org/lockingv3.html http://www.sqlite.org/sharedcache.html http://www.sqlite.org/atomiccommit.html Ro

[sqlite] Sqlite concurrency problem

Is it really correct that in order to perform an INSERT, Sqlite demands that no other connections be active? I have an application that loops through a results set and performs INSERTS. It uses the same database instance but (obviously) separate statements for each operation When the in