On 2 Nov 2017, at 16:56, Richard Hipp wrote: > Did you see this document: https://www.sqlite.org/undoredo.html
No, I didn't, thanks a lot. > Do the ideas talked about there help in any way? Yes, it's what we are seeking. The SESSIONs (sorry thought it's named VERSION) extension looks like something that will handle the tracking tables for us and create those change-sets as in the example. Storing change-sets inside the DB should work too, I think. Or would it be better to use the approach from the example and omit the SESSIONs extension at all? Viele Grüsse. -- Robert M. Münch, CEO M: +41 79 65 11 49 6 Saphirion AG smarter | better | faster http://www.saphirion.com http://www.nlpp.ch
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
