crawshaw.io/sqlite (go): Package sqlite provides a Go interface to SQLite 3.  The semantics of this package are deliberately close to the SQLite3 C API, so it is helpful to be familiar with http://www.sqlite.org/c3ref/intro.html.  An SQLite connection is represented by a *sqlite.Conn. Connections cannot be used concurrently. A typical Go program will create a pool of connections (using Open to create a *sqlitex.Pool) so goroutines can borrow a connection while they need to talk to the database.  This package assumes SQLite will be used concurrently by the process through several connections, so the build options for SQLite enable multi-threading and the shared cache: https://www.sqlite.org/sharedcache.html  The implementation automatically handles shared cache locking, see the documentation on Stmt.Step for details.  The optional SQLite3 compiled in are: FTS5, RTree, JSON1, Session, GeoPoly  This is not a database/sql driver.  Statements are prepared with the Prepare and PrepareTransient methods. When using Prepare, statements are keyed inside a connection by the original query string used to create them. This means long-running high-performance code paths can write:  After all the connections in a pool have been warmed up by passing through one of these Prepare calls, subsequent calls are simply a map lookup that returns an existing statement.  The sqlite package supports the SQLite incremental I/O interface for streaming blob data into and out of the the database without loading the entire blob into a single []byte. (This is important when working either with very large blobs, or more commonly, a large number of moderate-sized blobs concurrently.)  To write a blob, first use an INSERT statement to set the size of the blob and assign a rowid:  Use BindZeroBlob or SetZeroBlob to set the size of myblob. Then you can open the blob with:  Every connection can have a done channel associated with it using the SetInterrupt method. This is typically the channel returned by a context.Context Done method.  For example, a timeout can be associated with a connection session:  As database connections are long-lived, the SetInterrupt method can be called multiple times to reset the associated lifetime.  When using pools, the shorthand for associating a context with a connection is:  SQLite transactions have to be managed manually with this package by directly calling BEGIN / COMMIT / ROLLBACK or SAVEPOINT / RELEASE/ ROLLBACK. The sqlitex has a Savepoint function that helps automate this.  Using a Pool to execute SQL in a concurrent HTTP handler.  For helper functions that make some kinds of statements easier to write see the sqlitex package.
Keywords: golang|sqlite