Adam Megacz <[EMAIL PROTECTED]> wrote: > "Igor Tandetnik" <[EMAIL PROTECTED]> writes: >>>> Open a separate connection to the same database, perform the update >>>> on this connection. > > My understanding is that this second connection will block and then > time out if the first connection has a read operation in progress, so > I don't think this will actually work.
Didn't you say "Blocking for a long time is okay"? Just configure a really long timeout. > At this point it looks like having a thread that "goes to sleep" with > a read operation in progress basically makes it impossible for any > process to complete a write to the database. So don't let a thread go to sleep while it has a read operation in progress. If you want low contention, have each operation spend as little time in the database as possible. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
