Are you really proposing to restore just one or a selected set of tables from a backup of the database? What state does a transaction that touches one or more tables that are restored and one or more tables that aren't go to? It can't be "commited" because some data is not in the final state, and it can't be "rolled back" because some data is not in it's original state.
-----Ursprüngliche Nachricht----- Von: sqlite-users [mailto:[email protected]] Im Auftrag von Richard Damon Gesendet: Sonntag, 03. September 2017 19:13 An: [email protected] Betreff: [EXTERNAL] Re: [sqlite] SQLITE bug On 9/3/17 10:16 AM, Joseph L. Casale wrote: > -----Original Message----- > From: sqlite-users > [mailto:[email protected]] On Behalf Of R > Smith > Sent: Sunday, September 3, 2017 7:51 AM > To: [email protected] > Subject: Re: [sqlite] SQLITE bug > >> Lastly, a comment I've made possibly more than once on this list: >> There is no imperative to trust the SQL engine with ID assignments. >> You are free to (and I prefer to) assign IDs yourself. > What exactly do you feel you benefit by taking ownership of the ID, > specifically that of which you feel supersedes the obvious perils in the > cases you noted? One BIG example of a place to overrule the default ID assignment via auto-increment is in restoring a backup. Here, you NEED to ID to be the same as before so Foreign keys in other tables stay pointing to the right record. -- Richard Damon _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick Software Engineer Scientific Games International GmbH FN 157284 a, HG Wien Klitschgasse 2-4, A-1130 Vienna, Austria Tel: +43 1 80100 0 E-Mail: [email protected] This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
