This should finally unblock upgrading SQLite per se to latest release
once the builders are happy with this commit.

vendors libsqlite3@v1.8.0

write unit test for issue 209

See merge request cznic/sqlite!75

- doc.go: update SQLite version
- stmt.exec(): correct order of err assignment
- stmt.query(): do not finalite pstmt before it'll be used
- functionArguments(): do not copy from zero sized blob

fix: convert int64 column value to time.Time if necessary; providing compatibility with mattn/go-sqlite3

Signed-off-by: thediveo <thediveo@gmx.eu>

Signed-off-by: thediveo <thediveo@gmx.eu>

Signed-off-by: thediveo <thediveo@gmx.eu>

Signed-off-by: thediveo <thediveo@gmx.eu>

test: add vfs unit test

See merge request !78

Signed-off-by: thediveo <thediveo@gmx.eu>

fix: convert int64 column value to time.Time if necessary; providing...

Closes #214

See merge request cznic/sqlite!76

add support for automatic time to unix epoch integer conversion

See merge request cznic/sqlite!77

feat: pre-update hooks

See merge request cznic/sqlite!80

This is useful in the following situation:

* `query` function gets called
* SQL query is executed correctly, the `r` result (Rows) is set
* after that, but before `query` returns, `ctx` is canceled
* `interruptOnDone`’s goroutine catches the cancelation and signals
  the completion back to `query` by turning the atomic signaling
  variable `done` to 1
* `query` finishes and returns
* the anonymous deferred function patched here is popped off the
  deferred stack and executed

The current code, seeing that `done` is not zero, will overwrite `r`
(Rows) with `nil`, and that implies the Rows can never be `Close`d.

Unclosed Rows mean that read transactions never finish, and that
blocks the checkpointer process and cause the WAL to grow unbounded,
and other read queries to slow down unbounded.

https://sqlite.org/wal.html#avoiding_excessively_large_wal_files
("Checkpoint Starvation")

Signed-off-by: Silvio Moioli <silvio@moioli.net>

Signed-off-by: Silvio Moioli <silvio@moioli.net>
Co-authored-by: Alejandro Ruiz <alejandro.ruiz@suse.com>

Close Rows object if the context is canceled before deferred function

See merge request !81

- Introduce vtab subpackage (modernc.org/sqlite/vtab) exposing Module, Table,...

See merge request !84

The previous code was subject to a TOCTOU race:
the atomic.AddInt32 in the select statement could succeed,
but then context switch away before actually calling c.interrupt.
The actual call to c.interrupt could end up occurring later,
interrupting an unrelated subsequent query.

Fixes #241

fix TOCTOU interrupt race

Closes #241

See merge request !86

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.