On Mon, Dec 19, 2011 at 1:34 PM, Pavel Ivanov <paiva...@gmail.com> wrote: > > Yes, this is expected behavior. In this case transaction won't be able > to ever proceed because it can proceed only when writing transaction > in session 1 is committed but it cannot be committed until all reading > transactions are finished, including transaction in session 2. So it's > a deadlock and SQLite knows about that, thus it returns "database > locked" immediately.
Does anyone know if those who use SQLite with PHP need to be concerned with this issue (i.e. to program around this)? I've assumed that a PDO driver for SQLite or another layer will take care of waiting, retrying, etc. when needed. Is that a correct assumption? _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
