Hi! On 2018-10-05 18:47, Keith Medcalf wrote: > The experimental ENABLE_SNAPSHOT interface can do this sort-of. The > transaction still has to be in the WAL file (which means you may need to make > the WAL file persistent across closes using the appropriate file control). > However, you can only OPEN read-only snapshots in the past, you cannot roll > back to them.
According to my understanding of the docs I read, this is already available (non-experimentally), no? I thought that is basically what sqlite3_snapshot_get does. Unfortunately, that has indeed the problem that it seems to only allow me to read the old snapshot but not restore to it. > I do not think this is a built-in feature of SQLite3. Basically you want to > keep your own "list of changes" made to the database (as in a log) and within > a transaction apply those (or unapply those going backward in time) until you > arrive at the point it time you want. If you commit that transaction you > have restored to a previous point-in-time and should get rid of the log > entries after that point. Otherwise the "restored" snapshot is only > available to the one writer that has performed that "roll-back" operation > until the entire undo is released (ROLLACK). Exactly -- I can manually keep undo logs to perform the rollbacks, but I'm hoping that SQLite can do that for me. 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 [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
