On 2018-10-05 19:47, Daniel Kraft wrote: > I'm still thinking about the savepoints that Chris pointed out, though. > They seem to be very close to what I need. And even if I don't commit > the transaction, I imagine that at least the database connection that is > building it sees the updated state also for SELECT's, right? That's > enough for me since I only have a single-user situation anyway. > However, it seems that unfinished transactions / savepoints cannot be > persisted when closing the database (which I would need).
I did now a quick experiment with the sqlite3 command-line, and it seems that savepoints indeed work exactly what I need *except* for being non-persistent. Is there some way or trick I could use to make them (or the "current session") persist? Yours, Daniel -- https://www.domob.eu/ OpenPGP: 1142 850E 6DFF 65BA 63D6 88A8 B249 2AC4 A733 0737 Namecoin: id/domob -> https://nameid.org/?name=domob -- 3.6.0: Bar-Pri-Ran-Rog-Sam-Val-Wiz To go: Arc-Cav-Hea-Kni-Mon-Tou
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
