Releases: zombiezen/go-sqlite
Releases · zombiezen/go-sqlite
0.13.0
Version 0.13 added support for user-defined collating sequences and user-defined virtual tables.
Added
- Support user-defined collating sequences (#21).
- Support user-defined virtual tables (#15).
- New package
ext/generateseries
provides an optionalgenerate_series
table-valued function extension. - Exported the
regexp
function example as a newext/refunc
package. - Add
*Conn.Serialize
and*Conn.Deserialize
methods (#52).
Changed
- The minimum supported Go version for this library is now Go 1.19.
Fixed
- The documentation for
AggregateFunction.WindowValue
incorrectly stated that it would not be called in non-window contexts. The sentence has been removed, but the behavior has not changed.
0.12.0
Version 0.12 added support for the online backup API.
Added
- Added support for the online backup API (#47).
- Documented the
OpenFlags
.
Changed
OpenNoMutex
andOpenFullMutex
no longer have an effect onsqlite.OpenConn
.OpenNoMutex
(i.e. multi-thread mode) is now the only supported mode.*sqlite.Conn
has never been safe to use concurrently from multiple goroutines, so this is mostly to prevent unnecessary locking and to avoid confusion. (#32).
0.11.0
Version 0.11 changes the aggregate function API.
Changed
- User-defined aggregate functions are now encapsulated with a new interface,
AggregateFunction
. The previous 4-callback approach has been removed and replaced with a singleMakeAggregate
callback. Not only was the previous API unwieldy, but it failed to handle concurrent aggregate function calls in a single query. - Minimum
modernc.org/sqlite
version updated to 1.20.0.
0.11.0 beta 1
v0.11.0-beta1 Add AggregateFunction interface
0.10.1
0.10.0
Version 0.10 adds support for user-defined window functions.
Added
FunctionImpl
has two new fields (WindowValue
andWindowInverse
) that allow creating user-defined aggregate window functions (#42).
Changed
- The
AggregateStep
callback now returns anerror
.
0.9.3
0.9.2
Version 0.9 adds new Execute
functions to sqlitex
and changes the default blocking behavior. Version 0.9 also includes various fixes to the schema migration behavior.
Added
- Added
SetBlockOnBusy
method to set an indefinite timeout on acquiring a lock. - Official support for
windows/amd64
. sqlitex
has three new functions —Execute
,ExecuteTransient
, andExecuteScript
— that take in anExecOptions
struct. (#5)- New method
sqlite.ResultCode.ToError
to create error values. - New methods
ColumnBool
andGetBool
on*sqlite.Stmt
(#37).
Changed
OpenConn
callsSetBlockOnBusy
on new connections instead ofSetBusyTimeout(10 * time.Second)
.- The
sqlitex.Execute*
family of functions now verify that the arguments passed match the SQL parameters. (#31)
Deprecated
sqlitex.ExecFS
has been renamed tosqlitex.ExecuteFS
,sqlitex.ExecTransientFS
has been renamed tosqlitex.ExecuteTransientFS
, andsqlitex.ExecScriptFS
has been renamed tosqlitex.ExecuteScriptFS
for consistency with the newExecute
functions. Aliases remain in this version, but will be removed in the next version. Usezombiezen-sqlite-migrate
to clean up existing references.sqlitex.Exec
andsqlitex.ExecTransient
have been marked deprecated because they do not perform the argument checks that theExecute
functions now perform. These functions will remain into 1.0 and beyond for compatibility, but should not be used in new applications.
Fixed
sqlitemigration.Schema.RepeatableMigration
is now run as part of the final transaction. This ensures that the repeatable migration for migrationN
has executed if and only ifuser_version == N
. Previously, the repeatable migration could fail independently of the final transaction, which would mean that a subsequent migration run would not trigger a retry of the repeatable transaction, but report success.sqlitemigration
will no longer skip applying the repeatable migration if the final migration is empty.OpenConn
now sets a busy handler before enabling WAL (thanks @anacrolix!).
0.9.0 beta 1
Beta release of 0.9 (release notes). This release contains some changes that I want to experiment with in a few of my projects before finalizing the release, so I'm cutting a beta tag first.