Since _time_format=sqlite was introduced in
064df839 it has used (as described in that commit message):

> the time package format "2006-01-02 15:04:05.999999999-07:00".
> This is the format mattn/go-sqlite3 uses and is format 4 at
> https://sqlite.org/lang_datefunc.html#time_values.

A couple months later this parameter was documented in
8e27ffc8 as corresponding
to format 7 which is not and has never been the case
(format 7 has a T between the date and the time).

fix(docs): _time_format=sqlite corresponds to format 4

See merge request !91

- Enable configurable vtab options and add MATCH coverage. Expose Context.Config alongside EnableConstraintSupport, wire sqlite3_vtab_config through vtab create/connect, and document the new hook. Add a unit test ensuring MATCH constraints work when enabled.

Thanks HaoZi!

If a COMMIT fails (e.g. with SQLITE_BUSY), SQLite may leave the transaction
open, but database/sql expects the driver.Tx to be finished and the
underlying connection to be clean when Commit() returns.

This mismatch caused connection pool poisoning, where subsequent uses of
the connection would fail with "cannot start a transaction within a transaction".

This fix checks sqlite3_get_autocommit after a failed Commit. If the
transaction is still active, it forces a ROLLBACK to reset the connection
state, while still returning the original error to the caller.

Fixes https://github.com/modernc-org/sqlite/issues/2