Hi Shawn, > demonstrate SQLite best > practices, including how to correctly handle error conditions, such as > the database is locked condition?
> If you pre-select and then modify, you have to be aware enough to > realize you MUST wrap the whole process in a manual transaction, > and you still need to know how to deal with all the locking and > busy issues that come with that. One way to assure use of best-practices in dealing with SQLite nitty-gritties of transactions, locking and busy errors would be to use a tool like StepSqlite PL/SQL compiler (https://www.metatranz.com/stepsqlite). It automates SQLite best-practices (as recommended by Jay, Pavel and Simon in this thread) by wrapping things in transactions, handling BUSY errors and retrying after delay and others like preparing all SQL statements only once etc. SQLite combined with a 4GL like StepSqlite PL/SQL lets you focus on writing your code instead of having to learn to deal with SQLite idiosyncrasies right at the beginning. Full disclosure: I am the creator of StepSqlite. -Swapnil Kashikar support @ metatranz . com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
