[pull] master from mattn:master - #3

Do not use `-u` flag when fetching go-acc

seperated -> separated

The busy_timeout pragma was added in sqlite 3.7.15 as an alternative
to calling sqlite3_busy_timeout directly:

https://sqlite.org/pragma.html#pragma_busy_timeout

While there's no functional change here, using the pragma does align
setting busy_timeout with other settings and removes the special case
for calling sqlite3_busy_timeout directly.

uses snippet suggested by @rittneje #897 (comment)

* sqlite3_type update

The main reason for this change is that the original reflected values are nil. I found that there was no good mapping when dealing with the code here

* Update sqlite3_type.go

Update 'ColumnTypeScanType' method,
Different types of mapping values

* Restore copyright

* Update go.mod

* Update go.mod

Selecting only some tests with go test -run=... does not work, because
some of the tests are executed using testing.RunTests(). That function
is documented as "an internal function". This changes TestSuite to use
the testing subtests feature instead.

This has a behaviour change: the benchmarks now need to be
selected at the command line with the standard go test -bench=.
flag. This will also set up the test database twice when running
benchmarks, rather than once.

* Add go.mod and go.sum for upgrade

* Fix upgrade tools to have to run on upgrade directory

Currently, no way to fix failing

This commit adds the SQLiteConn.FileControlInt() method which calls the
underlying sqlite3_file_control() function with an int argument. This can
be used for low-level operations on SQLite databases such as persisting
the WAL file after database close.

…xample

Release vtable and cursor handles when SQLite destroys them

Do not clobber SQLite's default cost estimates in BestIndex

Translate SQL NULL filter arguments to nil like goVUpdate

Identify updated row by argv 0 in goVUpdate

Ignore Used for constraints SQLite marked not usable

Reject nil module and nil BestIndex result

Fail upgrade tool on download and write errors

Fix off-by-one truncating SQL in fuzz target

Fix wrong results and cursor state sharing in series example

Use the table name from xCreate args in vtable example

Close leaked rows in hook example

Close prepared statement and fail if limit is not enforced in limit example

Upgrade SQLite to version 3053004

Handle NULL and BLOB values in json example Scan

Add workflow to create releases on tag push

SQLite retains p->pVtab when xDestroy returns an error and later calls
xDisconnect on the same object (during sqlite3VtabUnlock or close).
Deleting the Go-side handle on the xDestroy error path made that later
xDisconnect panic with a nil type assertion in goVRelease.

Release the handle only after a successful xDestroy (or any xDisconnect,
where SQLite always discards the object). Found in the 0xCarbon fork's
SQLCipher sync; regression test panics on the previous code.

fix: keep vtab handle registered when xDestroy fails