On Mon, 2005-07-25 at 12:34 -0700, R S wrote: > Hi, > I have 2 process accessing the DB, one reading and the other > writing. Often the process reading the DB could take long and could > block the other process from committing a bunch of records to the DB. > I noticed that when the reader process has the lock and the writer > process tries to commit a bunch of records in the DB, the writer > blocks forever till it obtains the lock? Is this intended? I could > also always try to commit a little later and the approach works well > for my particular app. Can the behavior be changed? > Thanks. >
SQLite never blocks for any reason. If it cannot get a lock, it returns SQLITE_BUSY. Even if you call sqlite3_busy_timeout() it doesn't block - it polls. What OS are you using? What wrappers around SQLite are you using? What version of SQLite? -- D. Richard Hipp <[EMAIL PROTECTED]>