Samuel Neff <[EMAIL PROTECTED]> wrote: > If I launch two sqlite3.exe processes to the same database and do > "begin > exclusive" in one and "begin" in the second I do not get a > busy/locked error > in the second (not until you run some other sql like select or > insert).
BEGIN statement doesn't itself acquire any locks. It simply sets a flag in the connection to turn auto-commit off. > What situation can cause "begin" to get a busy/locked error? None that I can think of. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
