On 19 Jun 2019, at 3:39pm, Carsten Müncheberg <[email protected]> wrote:
> /* SQLITE_BUSY */ "database is locked", > /* SQLITE_LOCKED */ "database table is locked", With two different connections, either by the same program or different programs/computers, you will see SQLITE_BUSY . SQLITE_BUSY is subject to handling with timeouts set within SQLite. If your code simultaneously tries to use one database connection for two accesses (multi-threading), or two connections with shared cache, SQLite immediately returns a result of SQLITE_LOCKED without any attempt at pause and retry. This is explained in the SQLite documentation, but the explanation is spread out over several different pages. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
