Memory DB with transaction lost on canceled Context due to lack of SessionResetter, Validator

If a memory DB has an operation in progress in a transaction with a Context, and that context is canceled, the entire memory DB will be lost.

What?!

When a transaction is opened with a context, a background goroutine is started to roll back the transaction as soon as the context is Done(): https://github.com/golang/go/blob/release-branch.go1.16/src/database/sql/sql.go#L1786

If that rollback fires, it conditionally will close the corresponding connection based on whether the driver implements both driver.SessionResetter and driver.Validator: https://github.com/golang/go/blob/release-branch.go1.16/src/database/sql/sql.go#L1764-L1766

Since this package implements neither of those, any time a transaction against a memory connection is rolled back due to context cancellation, the entire database is lost ... unless you have other connections open and are using shared cache mode I guess. But that combination leads to endless "table is locked" errors and so is oft avoided.

My guess is that implementing these two interfaces would be pretty easy for SQLite?

Start with the transaction cancellation and rollback behavior described in the linked database/sql source, then inspect the driver’s handling of in-memory connections and the SessionResetter and Validator interfaces. Reproduce cancellation during a transaction and verify that the in-memory database remains available afterward, with tests covering the canceled-context case.