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). What situation can cause "begin" to get a busy/locked error? (plain begin, of course begin immediate or begin exclusive can get locked errors).
Thanks, Sam ----------------------------------------------------------------- We're Hiring! Seeking passionate Flex, C#, or C++ (RTSP, H264) developer. Position is in the Washington D.C. metro area. Contact [EMAIL PROTECTED] On Tue, Jun 10, 2008 at 6:04 PM, Ken <[EMAIL PROTECTED]> wrote: > Yes the BEGIN Transaction may get a BUSY/LOCKED error. > > If the BEGIN fails then do not commit, If you do commit you'll get an error > indicating that the commit failed due to no active transaction > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
