This has been a very informative and helpful discussion. Thank you. So have I understood correctly, that in an application, this kind of SQLITE_BUSY handling is sufficient:
BEGIN UPDATE #1 SELECT #2 UPDATE #3 COMMIT <----- check for busy here and retry only the commit on failure And second, what is the best place for busy-handling when only reading? Examle: BEGIN <---- sufficient here? SELECT #1 SELECT #2 SELECT #3 ROLLBACK Can I assume that if the "begin" succeeds, I have the right to perform all following selects without having to fear getting an SQLITE_BUSY? Or do I have to repeat the whole block? _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
