<https://www.sqlite.org/lang_transaction.html>
concerns me. I suspect it started out small and grew, without ever being rewritten. (1) It explains four complicated issues and has no sections. I see two possibilities: either improve that page, or split it into (A) a short page which discusses SQL syntax and API calls and (B) a separate long page which discusses how SQLite handles transactions. (2) Minor improvement: "Any command that changes the database [...] will automatically start a transaction if one is not already in effect.". Doesn't mention ending the transaction. Either that could be added, or perhaps the phrase that this list evolved "wraps the command in a transaction" might be used. (3) There's a single 12-sentence-long paragraph which describes the effects of using EXCLUSIVE and IMMEDIATE. It comes after mentioning the more obscure SAVEPOINT mechanism, and I suspect I understand it only because I already understood the subject from reading this list. Could there be two section headings in this document: one for the varieties of BEGIN, and the other for how SAVEPOINT and RELEASE fit into things ? The BEGIN section can say whether IMMEDIATE implies EXCLUSIVE, or vice versa, or neither. The SAVEPOINT section can explain expected orders for using BEGIN COMMIT ROLLBACK SAVEPOINT RELEASE, whether savepoints are nested or sequential, and such things. And also, whether unexpectedly closing a database does COMMIT RELEASE ROLLBACK if possible. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
