Latest stable version is v1.14 or later, not v2.
A sqlite3 driver that conforms to the built-in database/sql interface.
Supported Golang version: See .github/workflows/go.yaml.
This package follows the official Golang Release Policy.
This package can be installed with the go get command:
go get github.com/mattn/go-sqlite3
go-sqlite3 is cgo package. If you want to build your app using go-sqlite3, you need gcc.
Important: because this is a CGO enabled package, you are required to set the environment variable CGO_ENABLED=1 and have a gcc compiler present within your path.
API documentation can be found here.
Examples can be found under the examples directory.
When creating a new SQLite database or connection to an existing one, with the file name additional options can be given. This is also known as a DSN (Data Source Name) string.
Options are append after the filename of the SQLite database.
The database filename and options are separated by an ? (Question Mark).
Options should be URL-encoded (see url.QueryEscape).
This also applies when using an in-memory database instead of a file.
Options can be given using the following format: KEYWORD=VALUE and multiple options can be combined with the & ampersand.
This library supports DSN options of SQLite itself and provides additional options.
Boolean values can be one of:
* 0 no false off
* 1 yes true on
| Name | Key | Value(s) | Description |
|---|---|---|---|
| UA - Create | _auth |
- | Create User Authentication, for more information see User Authentication |
| UA - Username | _auth_user |
string |
Username for User Authentication, for more information see User Authentication |
| UA - Password | _auth_pass |
string |
Password for User Authentication, for more information see User Authentication |
| UA - Crypt | _auth_crypt |
|
Password encoder to use for User Authentication, for more information see User Authentication |
| UA - Salt | _auth_salt |
string |
Salt to use if the configure password encoder requires a salt, for User Authentication, for more information see User Authentication |
| Auto Vacuum | _auto_vacuum | _vacuum |
|
For more information see PRAGMA auto_vacuum |
| Busy Timeout | _busy_timeout | _timeout |
int |
Specify value for sqlite3_busy_timeout. For more information see PRAGMA busy_timeout |
| Case Sensitive LIKE | _case_sensitive_like | _cslike |
boolean |
For more information see PRAGMA case_sensitive_like |
| Defer Foreign Keys | _defer_foreign_keys | _defer_fk |
boolean |
For more information see PRAGMA defer_foreign_keys |
| Foreign Keys | _foreign_keys | _fk |
boolean |
For more information see PRAGMA foreign_keys |
| Ignore CHECK Constraints | _ignore_check_constraints |
boolean |
For more information see PRAGMA ignore_check_constraints |
| Immutable | immutable |
boolean |
For more information see Immutable |
| Journal Mode | _journal_mode | _journal |
|
For more information see PRAGMA journal_mode |
| Locking Mode | _locking_mode | _locking |
|
For more information see PRAGMA locking_mode |
| Mode | mode |
|
Access Mode of the database. For more information see SQLite Open |
| Mutex Locking | _mutex |
|
Specify mutex mode. |
| Query Only | _query_only |
boolean |
For more information see PRAGMA query_only |
| Recursive Triggers | _recursive_triggers | _rt |
boolean |
For more information see PRAGMA recursive_triggers |
| Secure Delete | _secure_delete |
boolean | FAST |
For more information see PRAGMA secure_delete |
| Shared-Cache Mode | cache |
|
Set cache mode for more information see sqlite.org |
| Synchronous | _synchronous | _sync |
|
For more information see PRAGMA synchronous |
| Time Zone Location | _loc |
auto | Specify location of time format. |
| Transaction Lock | _txlock |
|
Specify locking behavior for transactions. |
| Writable Schema | _writable_schema |
Boolean |
When this pragma is on, the SQLITE_MASTER tables in which database can be changed using ordinary UPDATE, INSERT, and DELETE statements. Warning: misuse of this pragma can easily result in a corrupt database file. |
| Cache Size | _cache_size |
int |
Maximum cache size; default is 2000K (2M). See PRAGMA cache_size |
| Statement Cache Size | _stmt_cache_size |
int |
Maximum number of prepared statements cached per connection; default is 0 (disabled). Note that sql.DB is a connection pool, so each connection maintains its own independent cache. |
file:test.db?cache=shared&mode=memory
This package allows additional configuration of features available within SQLite3 to be enabled or disabled by golang build constraints also known as build tags.
Click here for more information about build tags / constraints.
If you wish to build this library with additional extensions / features, use the following command:
go build -tags "<FEATURE>"
For available features, see the extension list. When using multiple build tags, all the different tags should be space delimited.
Example:
go build -tags "icu json1 fts5 secure_delete"
| Extension | Build Tag | Description |
|---|---|---|
| Additional Statistics | sqlite_stat4 | This option adds additional logic to the ANALYZE command and to the query planner that can help SQLite to chose a better query plan under certain situations. The ANALYZE command is enhanced to collect histogram data from all columns of every index and store that data in the sqlite_stat4 table. |
The query planner will then use the histogram data to help it make better index choices. The downside of this compile-time option is that it violates the query planner stability guarantee making it more difficult to ensure consistent performance in mass-produced applications.
SQLITE_ENABLE_STAT4 is an enhancement of SQLITE_ENABLE_STAT3. STAT3 only recorded histogram data for the left-most column of each index whereas the STAT4 enhancement records histogram data from all columns of each index.
The SQLITE_ENABLE_STAT3 compile-time option is a no-op and is ignored if the SQLITE_ENABLE_STAT4 compile-time option is used | | Allow URI Authority | sqlite_allow_uri_authority | URI filenames normally throws an error if the authority section is not either empty or "localhost".
However, if SQLite is compiled with the SQLITE_ALLOW_URI_AUTHORITY compile-time option, then the URI is converted into a Uniform Naming Convention (UNC) filename and passed down to the underlying operating system that way | | App Armor | sqlite_app_armor | When defined, this C-preprocessor macro activates extra code that attempts to detect misuse of the SQLite API, such as passing in NULL pointers to required parameters or using objects after they have been destroyed.
App Armor is not available under Windows. |
| Disable Load Extensions | sqlite_omit_load_extension | Loading of external extensions is enabled by default.
To disable extension loading add the build tag sqlite_omit_load_extension. |
| Enable Serialization with libsqlite3 | sqlite_serialize | Serialization and deserialization of a SQLite database is available by default, unless the build tag libsqlite3 is set.
To enable this functionality even if libsqlite3 is set, add the build tag sqlite_serialize. |
| Foreign Keys | sqlite_foreign_keys | This macro determines whether enforcement of foreign key constraints is enabled or disabled by default for new database connections.
Each database connection can always turn enforcement of foreign key constraints on and off and run-time using the foreign_keys pragma.
Enforcement of foreign key constraints is normally off by default, but if this compile-time parameter is set to 1, enforcement of foreign key constraints will be on by default | | Full Auto Vacuum | sqlite_vacuum_full | Set the default auto vacuum to full | | Incremental Auto Vacuum | sqlite_vacuum_incr | Set the default auto vacuum to incremental | | Full Text Search Engine | sqlite_fts5 | When this option is defined in the amalgamation, versions 5 of the full-text search engine (fts5) is added to the build automatically | | International Components for Unicode | sqlite_icu | This option causes the International Components for Unicode or "ICU" extension to SQLite to be added to the build | | Introspect PRAGMAS | sqlite_introspect | This option adds some extra PRAGMA statements.
When this option is not used, secure_delete defaults to off. When this option is present, secure_delete defaults to on.
The secure_delete setting causes deleted content to be overwritten with zeros. There is a small performance penalty since additional I/O must occur.
On the other hand, secure_delete can prevent fragments of sensitive information from lingering in unused parts of the database file after it has been delete
$ claude mcp add go-sqlite3 \
-- python -m otcore.mcp_server <graph>