Description
I learned about the session extension from https://github.com/crawshaw/sqlite. The SQLite documentation says:
The session extension provide a mechanism for recording changes to some or all of the rowid tables in an SQLite database, and packaging those changes into a "changeset" or "patchset" file that can later be used to apply the same set of changes to another database with the same schema and compatible starting data. A "changeset" may also be inverted and used to "undo" a session.
...
In other words, the session extension provides a facility for SQLite database files that is similar to the unix patch utility program, or to the "merge" capabilities of version control systems such as Fossil, Git, or Mercurial.
This enables, for example, synching the database between different applications over the network in an efficient way (only the delta, not the whole db).
To work, the session must be created. This makes the extension start recording the changesets.
I was wondering if you see value in supporting this extension, and if from a technical point of view this can be done while still being compatible with database/sql.
Personally, I would love this support :-)