Re: [sqlite] Sqlite3 & Concurrency

2014-04-23 Thread Simon Slavin
On 23 Apr 2014, at 10:42am, techi eth wrote: > Many Thanks for quick reply. > > Could you please suggest me other journal mode for second case.My target > filesytem dosen't support mmap & WAL required mmap support.

Re: [sqlite] Sqlite3 & Concurrency

2014-04-23 Thread techi eth
Many Thanks for quick reply. Could you please suggest me other journal mode for second case.My target filesytem dosen't support mmap & WAL required mmap support. Thanks On Wed, Apr 23, 2014 at 3:05 PM, Simon Slavin wrote: > > On 23 Apr 2014, at 10:29am, techi eth

Re: [sqlite] Sqlite3 & Concurrency

2014-04-23 Thread Simon Slavin
On 23 Apr 2014, at 10:29am, techi eth wrote: > 1) Sqlite3 doesn’t have any concurrency issue when multiple process > reading one database file at same time. This doesn’t required any special > mode setting (Like WAL) Correct. > 2) One process is reading & other

[sqlite] Sqlite3 & Concurrency

2014-04-23 Thread techi eth
Hi, Please correct me on below points for Sqlite3 on Linux platform. 1) Sqlite3 doesn’t have any concurrency issue when multiple process reading one database file at same time. This doesn’t required any special mode setting (Like WAL) 2) One process is reading & other process

Re: [sqlite] SQLite3 Concurrency

2007-08-26 Thread John Stanton
You need to be prepared to get a busy status after each Sqlite3_step. If you launch a sqlite3_step while a transaction which is executing an INSERT or UPDATE is current, you will get an SQLITE_BUSY. If you get a BUSY, try again until the condition clears. Igor Mironchick wrote: Hi, guys. I

[sqlite] SQLite3 Concurrency

2007-08-26 Thread Igor Mironchick
Hi, guys. I have some questions about multithreading in SQLite: a) If one thread "BEGIN" and after that another thread try to "BEGIN". What will with the second thread? How I understand there is nothing wrong. Is it right? b) The same one only when second thread "BEGIN" after first thread