David Barrett <[EMAIL PROTECTED]> wrote: > Igor Tandetnik wrote: >> SQLite detects deadlock situation. The call trying to execute the >> update statement fails immediately with SQLITE_BUSY error. Neither >> transaction releases its locks: to make progress, one of them has to >> explicitly roll back. > > Aha, got it. One more question: take the same scenario as before, but > now have two distinct tables (barA and barB) inside the same database,
Makes no difference: SQLite locks at file level, not table level. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
