aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* sqlite3.go: use PRAGMA to set busy_timeout (#910)Dan Peterson2021-10-261-6/+6
| | | | | | | | | | 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.
* Test on 1.17Yasuhiro Matsumoto2021-10-261-1/+1
|
* run tests against Go 1.16 (#967)Harry2021-10-261-2/+2
|
* Fix typo in README.md (#939)Ikko Ashimine2021-10-260-0/+0
| | | seperated -> separated
* Resolve windows CI issues (#941)hackerman2021-10-261-1/+1
| | | Do not use `-u` flag when fetching go-acc
* Allow building on OpenBSD (#976)Denis Fondras2021-10-261-0/+2
|
* chore: readme: Fix link, typos, copy editing (#974)Ross Smith II2021-10-221-56/+55
| | | | | | | * chore: readme: Fix link, typos, copy editing Also closes #914, #939. * Update README.md
* return non-nil result when calling exec with empty query (#973)Aviv Klasquin Komissar2021-10-192-0/+24
| | | fixes #963
* bump codecov/codecov-action@v2 (#957)Ichinose Shogo2021-07-201-1/+1
|
* Update amalgamation code (#955)mattn2021-07-154-2972/+4357
| | | | | * Update amalgamation code * Apply realPy's patch
* Update amalgamation code (#940)mattn2021-04-152-4655/+7157
|
* make column metadata functionality opt-inJesse Rittner2021-02-185-44/+61
|
* Export sqlite3_column_table_name (#900)Philip O'Toole2021-02-182-0/+43
|
* Go get go-acc with environment variable for go modules (#915)Catena cyber2021-02-161-2/+2
| | | | | * Go get go-acc with environment variable for go modules * Go get with modules for windows as well
* Adds a fuzz target (#908)Catena cyber2021-02-152-1/+31
| | | | | * Adds a fuzz target * Fixes memory leak
* Export sqlite3_stmt_readonly() via SQLiteStmt.Readonly() (#895)Martin Tournoij2020-12-282-0/+48
| | | | | | | | | | | | | | | This can be used like in the test; I wrote a little wrapper around sql.DB which uses this, and allows concurrent reads but just one single write. This is perhaps a better generic "table locked"-solution than setting the connections to 1 and/or cache=shared (although even better would be to design your app in such a way that this doesn't happpen in the first place, but even then a little seat belt isn't a bad thing). The parsing adds about 0.1ms to 0.2ms of overhead in the wrapper, which isn't too bad (and it caches the results, so only needs to do this once). At any rate, I can't really access functions from sqlite3-binding.c from my application, so expose it via SQLiteStmt.
* Update amalgamation code (#896)mattn2020-12-263-728/+2032
|
* add support for defining an "eponymous only" virtual table (#885)Patrick DeVivo2020-12-264-3/+325
| | | | | | | | | * add support for defining an "eponymous only" virtual table As suggested here: https://github.com/mattn/go-sqlite3/issues/846#issuecomment-736206222 * add an example of an eponymous only vtab module * add a test case for an eponymous only vtab module
* RowsColumnTypeNullable not implemented (#848)Jinzhu2020-12-261-2/+2
|
* Add ?_cache_size=[..] to connection parameters (#894)Martin Tournoij2020-12-262-0/+23
| | | | | | | | | | | | | | | | | | Add a shortcut for PRAGMA cache_size; this is a pretty useful setting: the default of -2000 (2M) is not especially high, and a lot of people will probably want to increase this. For example, while running a bunch of fairy expensive queries in parallel: With SetMaxOpenConns(1): -2000: 5762ms -20000: 4714ms With SetMaxOpenConns(20): -2000: 3067ms -20000: 2532ms Which isn't a bad performance boost for changing a single number.
* clarify usleep license (#893)Brad Rydzewski2020-12-261-1/+3
|
* Fix ciYasuhiro Matsumoto2020-11-181-2/+2
|
* Drop go1.11 (#852)mattn2020-11-172-3/+3
| | | | | * Drop go1.11 * Use go1.12
* README.md: use link in markdown (#859)Buk Bukowski2020-11-171-1/+1
|
* sqlite3.go: Remove -DSQLITE_ENABLE_FTS4_UNICODE61: not supported (#872)Evan Jones2020-11-171-1/+0
| | | | | | | | | This option was enabled by default in sqlite3 on 2014-07-03. This setting does nothing. It can now be disabled with SQLITE_DISABLE_FTS3_UNICODE. See the upstream commit: https://sqlite.org/src/info/0cc0230ae9cfc976 I think this change was imported into this project with commit ee9da4840dd680d1fe2927692ea4ab5f8cd7c91c on 2015-06-12.
* sqlite3.go: remove -DSQLITE_DISABLE_INTRINSIC: better builds (#878)Evan Jones2020-11-171-1/+0
| | | | | | | | | | | | | | | | | | | | | | | This "disables the use of compiler-specific built-in functions such as __builtin_bswap32()" (from the SQLite docs) so this change might produce slightly better code. My primary motivation, however, is that the "default" configuration for SQLite, which is widely tested, does not set this preprocessor macro. From looking at Github issues, it appears this was added to avoid a build error on Mac OS X 10.11, in 2017: https://github.com/mattn/go-sqlite3/issues/386 There have been a number of changes to sqlite3 since we tried this last. I think it would be worth trying to remove this setting again. I found a machine running Mac OS X 10.11.6. It was able to build and run the tests in this package with this change. Mac OS X 10.11 is has not been supported by Apple since 2018 (currently Apple is releasing updates for Mac OS 10.13 and newer; 11 is the current release). However, Go 1.14 is supported, and it requires Mac OS X 10.11 or newer: https://golang.org/doc/go1.14 Go 1.15 only supports Mac OS 10.12 and newer: https://golang.org/doc/go1.15
* .github/workflows: stop using deprecated add-path command (#873)Evan Jones2020-11-171-2/+2
| | | | | | | | | | | | | | | | Github is disabling the add-path command in workflows on 2020-11-16. Switch to their new preferred way of doing this, by appending to the file referred to with $GITHUB_PATH. See: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/ https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-commands-for-github-actions#adding-a-system-path This should fix the following warning from the workflows: .github#L1 The `add-path` command is deprecated and will be disabled on November 16th. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
* Support vfs for Open (#877)mattn2020-11-172-1/+49
| | | Closes #876
* TestExecContextCancel: Reduce timeout to make less flaky (#879)Evan Jones2020-11-171-4/+10
| | | | | | | | | | | | | This test fails fairly often. On my system, I can trigger it with: go test . -run=TestExecContextCancel -count=10 -failfast -v This makes the test less flaky by timing out the context after a consistent 50 millisecond delay. This was enough time for the query to start, then get cancelled with sqlite3_interrupt() in my tests. This now passes the above check. This is a modified version of the change suggested in: https://github.com/mattn/go-sqlite3/pull/865
* sqlite3_test.go: Move Go 1.13 test to sqlite3_go113_test.go (#883)Evan Jones2020-11-173-31/+5
| | | | | | | | | Commit 4f7abea96e added a test that uses Conn.Raw, which was added in Go >= 1.13. The go-sqlite3 project runs tests with Go >= 1.11. Remove the test from sqlite3_test.go, so it only runs with the correct versions of Go. Instead of adding a new test, modify the existing test that already uses Conn.Raw() to check the type of driverConn.
* doc.go: you can use Conn.Raw to get *SQLiteConn (#882)Evan Jones2020-11-162-3/+43
| | | | This can be easier that registering a new driver, in some cases. Add a test to verify that this works.
* Expand documentation for extension functions (#880)Macaully James Muir2020-11-161-3/+16
| | | | This relates to #870; it's not immediately clear that you need to pass a different driver name to sql.Open from the documentation.
* Fix #860 extenstion entry bug (#861)Yunus Ayar2020-10-021-1/+1
| | | Fix overshadowing of entrypoint variable.
* Add build tag ignore for upgrade script (#851)mattn2020-09-113-19/+1
|
* Fix "cannot start a transaction within a transaction" issue (#764) (#765)Andrii Zavorotnii2020-08-293-6/+129
| | | | | | | | | | | | | | | | | | | | | * Fix "cannot start a transaction within a transaction" issue [why] If db.BeginTx(ctx, nil) context is cancelled too fast, "BEGIN" statement can be completed inside DB, but we still try to cancel it with sqlite3_interrupt. In such case we get context.Cancelled or context.DeadlineExceeded from exec(), but operation really completed. Connection returned into pool, and returns "cannot start a transaction within a transaction" error for next db.BeginTx() call. [how] Handle status code returned from cancelled operation. [testing] Added unit-test which reproduces issue. * Reduce TestQueryRowContextCancelParallel concurrency [why] Tests times out in travis-ci when run with -race option.
* Use go-pointer instead of uintptr hacks. (#814)mattn2020-08-263-53/+47
| | | | | | | | | | | | | * Use go-pointer instead of uintptr hacks. Fixes #791 * Do same of go-pointer * Drop older verion of Go * Fix build * Fix build
* treat vtable C arrays as Go slices rather than giant Go arrays (#840)rittneje2020-08-261-11/+21
|
* coveralls to codecov (#845)raa01212020-08-253-42/+35
| | | | | * coveralls to codecov * README badge coveralls to codecov
* Fix go.yamlYasuhiro Matsumoto2020-08-251-76/+76
|
* Update README.mdYasuhiro Matsumoto2020-08-251-2/+2
|
* Add Github Actions yaml and set LDFLAGS on windows (#843)raa01212020-08-253-36/+132
| | | and remove .travis.yml
* Update amalgamation code (#842)mattn2020-08-193-9975/+10880
| | | | | * Update amalgamation code * Drop go1.9 and go1.10
* Travis-CI: set go_import_path (#829)Olivier Mengué2020-07-211-0/+2
| | | | | Set go_import_path to tell Travis-CI where to checkout the code, so the Travis build can also work on forks. This is important when building without Go modules support.
* Travis-CI: add Go 1.14.x, change order of Go versions (#830)Olivier Mengué2020-07-211-5/+6
| | | | | | | Changes in Go versions for the Travis-CI builds: - reverse order of Go versions so the latest ones are checked first - add Go 1.14.x (latest stable) at the first position - use 'tip' instead of 'master' (like https://tip.golang.org) and move it just after 1.14.x
* Update README.mdYasuhiro Matsumoto2020-06-181-1/+3
|
* upgrade amalgamation code (#821)mattn2020-06-063-1844/+3104
|
* Add mock versions of SQLiteDriver and SQLiteConn for +build !cgo (#819)Martin Tournoij2020-06-051-7/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | My app can use PostgreSQL and – optionally – SQLite. I would like to be able to compile the app without cgo when SQLite isn't used, as this removes the need for a C compiler which makes builds easier and faster, especially for end-users. In the simple case, this is not a problem go-sqlite3 already provides a simple non-cgo mock so it compiles and gives a runtime error if you try to use it anyway. However, now I'd like to register a function for my SQLite connection to match a PostgreSQL function like so: sql.Register("sqlite3_custom", &sqlite3.SQLiteDriver{ ConnectHook: func(conn *sqlite3.SQLiteConn) error { return conn.RegisterFunc("pow", pow, true); err != nil { }, }) But this makes it quite hard to keep the same logic since it refers to types that don't exist with CGO_ENABLED=0. I will need to create a db.go with `+build !cgo` and db_cgo.go with `+buid cgo` which duplicates all the logic but with the sqlite hooks. In my case, this actually affects quite a lot; for example I have a helper function which connects and runs migrations and whatnot which looks like: type ConnectOptions struct { Connect string // Connect string. Schema []byte // Database schema to create on startup. Migrate *Migrate SQLiteHook func(*sqlite3.SQLiteConn) error } And I'd have to have two versions of that, too. You could perhaps do something with interfaces, but because the sql.Register() call above references the `sqlite3.SQLiteDriver.ConnectHook` struct field that's not so straightforward (and wrapping stuff in interfaces probably won't do much for the general clarity either). This simplifies all of that by providing some common types that may be used when setting up a SQLite connectin. I renamed the `SQLiteDriverMock` to `&SQLiteDriver` for this reason. As far as I can tell in my testing, this has no real downsides (but perhaps I missed something?) --- Note: it might also be worth doing something similar for error.go, as I already have two variants of the below function (one with cgo as below, and one without cgo which checks just PostgreSQL): // ErrUnique reports if this error reports a UNIQUE constraint violation. // // This is the cgo version which works for PostgreSQL and SQLite. func ErrUnique(err error) bool { var sqlErr *sqlite3.Error if errors.As(err, &sqlErr) && sqlErr.ExtendedCode == sqlite3.ErrConstraintUnique { return true } var pqErr *pq.Error if errors.As(err, &pqErr) && pqErr.Code == "23505" { return true } return false } This is a lot more manageable than the ConnectHook case, but it would be nicer if it would work without the need for build tags.
* Edited note in README (#817)turtlemaster192020-06-011-1/+1
|
* Document requirements for cross compiling from OSX (#804)Vishnu Mohandas2020-05-161-3/+9
| | | | | | | * Document requirements for cross compiling from OSX Inspiration: https://github.com/mattn/go-sqlite3/issues/384#issuecomment-433584967 * Document cross compilation steps using xgo for MACOSX
* Enable all prefixes for named parameters and allow for unused named ↵gber2020-05-142-53/+116
| | | | | | | | | | | | | parameters (#811) * Allow unused named parameters Try to bind all named parameters and ignore those not used. * Allow "@" and "$" for named parameters * Add tests for named parameters Co-authored-by: Guido Berhoerster <guido+go-sqlite3@berhoerster.name>
generated by cgit v1.2.3 (git 2.50.1) at 2026-01-04 02:49:47 +0000