You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sqlite3 driver conforming to the built-in database/sql interface
13
12
14
-
Installation
15
-
------------
13
+
### Overview
14
+
15
+
-[Installation](#installation)
16
+
-[API Reference](#api-reference)
17
+
-[Features](#features)
18
+
-[FAQ](#faq)
19
+
-[License](#license)
20
+
21
+
# Installation
16
22
17
23
This package can be installed with the go get command:
18
24
@@ -22,56 +28,80 @@ _go-sqlite3_ is *cgo* package.
22
28
If you want to build your app using go-sqlite3, you need gcc.
23
29
However, after you have built and installed _go-sqlite3_ with `go install github.com/mattn/go-sqlite3` (which requires gcc), you can build your app without relying on gcc in future.
24
30
25
-
Documentation
26
-
-------------
31
+
# API Reference
27
32
28
33
API documentation can be found here: http://godoc.org/github.com/mattn/go-sqlite3
29
34
30
-
Examples can be found under the `./_example` directory
35
+
Examples can be found under the [examples](./_example) directory
36
+
37
+
# Features
38
+
39
+
This package allows additional configuration of features available within SQLite3 to be enabled or disabled by golang build constraints also known as build `tags`.
31
40
32
-
FAQ
33
-
---
41
+
[Click here for more information about build tags / constraints.](https://golang.org/pkg/go/build/#hdr-Build_Constraints)
34
42
35
-
* Want to build go-sqlite3 with libsqlite3 on my linux.
43
+
| Extension | Build Tag | Description |
44
+
|-----------|-----------|-------------|
45
+
| 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.<br><br>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.<br><br>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.<br><br>The SQLITE_ENABLE_STAT3 compile-time option is a no-op and is ignored if the SQLITE_ENABLE_STAT4 compile-time option is used |
46
+
| Allow URI Authority | sqlite_allow_uri_authority | URI filenames normally throws an error if the authority section is not either empty or "localhost".<br><br>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 |
47
+
| 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. <br><br>App Armor is not available under `Windows`. |
48
+
| Disable Load Extensions | sqlite_omit_load_extension | Loading of external extensions is enabled by default.<br><br>To disable extension loading add the build tag `sqlite_omit_load_extension`. |
49
+
| Foreign Keys | sqlite_foreign_keys | This macro determines whether enforcement of foreign key constraints is enabled or disabled by default for new database connections.<br><br>Each database connection can always turn enforcement of foreign key constraints on and off and run-time using the foreign_keys pragma.<br><br>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 |
50
+
| Full Auto Vacuum | sqlite_vacuum_full | Set the default auto vacuum to full |
51
+
| Incremental Auto Vacuum | sqlite_vacuum_incr | Set the default auto vacuum to incremental |
52
+
| 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 |
53
+
| 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 |
54
+
| Introspect PRAGMAS | sqlite_introspect | This option adds some extra PRAGMA statements. <ul><li>PRAGMA function_list</li><li>PRAGMA module_list</li><li>PRAGMA pragma_list</li></ul> |
55
+
| JSON SQL Functions | sqlite_json | When this option is defined in the amalgamation, the JSON SQL functions are added to the build automatically |
56
+
| Secure Delete | sqlite_secure_delete | This compile-time option changes the default setting of the secure_delete pragma.<br><br>When this option is not used, secure_delete defaults to off. When this option is present, secure_delete defaults to on.<br><br>The secure_delete setting causes deleted content to be overwritten with zeros. There is a small performance penalty since additional I/O must occur.<br><br>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 deleted. See the documentation on the secure_delete pragma for additional information |
> See also: http://www.limitlessfx.com/cross-compile-golang-app-for-windows-from-linux.html
65
95
66
-
* Want to get time.Time with current locale
96
+
- Want to get time.Time with current locale
67
97
68
98
Use `_loc=auto` in SQLite3 filename schema like `file:foo.db?_loc=auto`.
69
99
70
-
* Can I use this in multiple routines concurrently?
100
+
- Can I use this in multiple routines concurrently?
71
101
72
102
Yes for readonly. But, No for writable. See [#50](https://github.com/mattn/go-sqlite3/issues/50), [#51](https://github.com/mattn/go-sqlite3/issues/51), [#209](https://github.com/mattn/go-sqlite3/issues/209), [#274](https://github.com/mattn/go-sqlite3/issues/274).
73
103
74
-
* Why is it racy if I use a `sql.Open("sqlite3", ":memory:")` database?
104
+
- Why is it racy if I use a `sql.Open("sqlite3", ":memory:")` database?
75
105
76
106
Each connection to :memory: opens a brand new in-memory sql database, so if
77
107
the stdlib's sql engine happens to open another connection and you've only
@@ -80,8 +110,7 @@ FAQ
80
110
connection to this string will point to the same in-memory database. See
81
111
[#204](https://github.com/mattn/go-sqlite3/issues/204) for more info.
82
112
83
-
License
84
-
-------
113
+
# License
85
114
86
115
MIT: http://mattn.mit-license.org/2012
87
116
@@ -91,7 +120,6 @@ The -binding suffix was added to avoid build failures under gccgo.
91
120
92
121
In this repository, those files are an amalgamation of code that was copied from SQLite3. The license of that code is the same as the license of SQLite3.
0 commit comments