aboutsummaryrefslogtreecommitdiff
Commit message (Expand)AuthorAgeFilesLines
* Add Github Actions yaml and set LDFLAGS on windows (#843)•••and remove .travis.ymlraa01212020-08-253-36/+132
* Update amalgamation code (#842)•••* Update amalgamation code * Drop go1.9 and go1.10mattn2020-08-193-9975/+10880
* Travis-CI: set go_import_path (#829)•••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.Olivier Mengué2020-07-211-0/+2
* Travis-CI: add Go 1.14.x, change order of Go versions (#830)•••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.xOlivier Mengué2020-07-211-5/+6
* 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)•••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.Martin Tournoij2020-06-051-7/+18
* Edited note in README (#817)turtlemaster192020-06-011-1/+1
* Document requirements for cross compiling from OSX (#804)•••* 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 MACOSXVishnu Mohandas2020-05-161-3/+9
* Enable all prefixes for named parameters and allow for unused named parameter...•••* 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>gber2020-05-142-53/+116
* Fix #808: remove goconvey (#809)•••* don't need smartystreets/goconvey any longer * synchronise coverallsDiego Becciolini2020-05-141-2/+4
* Fix for early termination of returned rows (#805)•••Once the regex encountered the first instance of a non-match, it would return without processing the rest of the rows in the statement. This change allows it to process the remaining, only setting the sqlite3_result_int to zero then continuing. This worked fine for the example as it only had one item to process.ShanePerron2020-05-031-1/+5
* report actual error message if sqlite3_load_extension fails (#800)•••* report actual error message if sqlite3_load_extension fails * more fixes and test cases Co-authored-by: Jesse Rittner <jrittner@lutron.com>rittneje2020-04-165-25/+112
* Add extension-functions.c info to README (#779)Paul Bergeron2020-04-161-0/+10
* Update dependenciesYasuhiro Matsumoto2020-04-162-1/+7
* feat: add go modules (#781)•••* feat: add go modules * feat: upgrade goquery dependencyKarthik K2020-04-162-0/+15
* chore: remove debug code (#788)Manfred Touron2020-02-271-2/+0
* upgrade amalgamation code (#777)mattn2020-01-283-5410/+9036
* Update README.mdYasuhiro Matsumoto2020-01-231-0/+2
* Fix typo (#763)Sergey Bronnikov2020-01-091-4/+4
* fix typo in doc comment (#770)rittneje2019-12-171-3/+3
* add SystemErrno to Error (#740)•••* adding SystemErrno to Error, and fixing error logic when open fails * fix for old versions of libsqlite3 that do not have sqlite3_system_errno defined * fixing pre-processor logic rittneje2019-12-174-12/+77
* Merge pull request #744 from azavorotnii/ctx_cancel•••Fix context cancellation racy handlingmattn2019-11-192-37/+147
|\
| * Fix context cancellation racy handling•••[why] Context cancellation goroutine is not in sync with Next() method lifetime. It leads to sql.ErrNoRows instead of context.Canceled often (easy to reproduce). It leads to interruption of next query executed on same connection (harder to reproduce). [how] Do query in goroutine, wait when interruption done. [testing] Add unit test that reproduces error cases. Andrii Zavorotnii2019-09-062-37/+147
* | Merge pull request #760 from mattn/sqlite-amalgamation-3300100•••upgrade amalgamation codemattn2019-11-193-3965/+5309
|\ \
| * | upgrade amalgamation codeYasuhiro Matsumoto2019-11-183-3965/+5309
|/ /
* | Merge pull request #758 from mattn/noncgo•••Add build constraints for non cgomattn2019-11-1841-40/+69
|\ \
| * | Add build constraints for non cgoYasuhiro Matsumoto2019-11-1841-40/+69
|/ /
* | Merge pull request #754 from codesoap/master•••Improve readability of Backup()mattn2019-11-051-3/+3
|\ \
| * | Improve readability of Backup()codesoap2019-10-311-3/+3
|/ /
* | Merge pull request #753 from opencollective/opencollective•••Activating Open Collectivemattn2019-10-311-0/+31
|\ \
| * | Added financial contributors to the READMEJess2019-10-301-0/+31
|/ /
* | Update FUNDING.ymlmattn2019-10-081-1/+1
* | Merge pull request #750 from tpounds/add-new-go-vers•••Add Go 1.12.x/1.13.x to CImattn2019-10-081-0/+2
|\ \
| * | Add Go 1.12.x/1.13.x to CI.Trevor Pounds2019-10-071-0/+2
|/ /
* | Merge pull request #747 from azavorotnii/open_journal_mode•••Fix Open() journal mode regressionmattn2019-09-241-6/+7
|\ \ | |/ |/|
| * Fix typo in "_locking_mode" DSN handlingAndrii Zavorotnii2019-09-231-1/+1
| * Fix Open() journal mode regression•••[why] see https://github.com/mattn/go-sqlite3/issues/607 SQLite default journal mode is DELETE, but forcing it on open causes "database is locked" if other connection exists with WAL mode, for example. [how] Don't set DELETE mode if not set in DSN explicitly. [testing] Run tests in my project where WAL mode is used. Andrii Zavorotnii2019-09-231-5/+6
|/
* Fix memory leak in ExpandedSQL (#738)•••Fixes: #733Gert-Jan Timmer2019-08-221-0/+1
* Fixed operatorG.J.R. Timmer2019-08-221-2/+2
* Fix _auth_* parameter check•••Fixes: #724G.J.R. Timmer2019-08-222-3/+27
* Closes #597G.J.R. Timmer2019-08-228-9/+623
* Merge pull request #734 from gwd/out/fix-libsqlite3-darwin-build•••darwin/libsqlite3: Also use the homebrew include pathmattn2019-08-201-0/+1
|\
| * darwin/libsqlite3: Also use the homebrew include path•••When building on darwin with the `libsqlite3` tag, go-sqlite3 adds the homebrew library path. It does not, however, add the homebrew include path, which means that the MacOS sqlite3 header is used instead. On my system, this results in build errors that look like this: ./sqlite3_load_extension.go:25:8: could not determine kind of name for C.sqlite3_enable_load_extension ./sqlite3_load_extension.go:33:8: could not determine kind of name for C.sqlite3_load_extension Add the homebrew include path as well, so that he header matches the libraries we're using. Signed-off-by: George Dunlap <george.dunlap@citrix.com> George Dunlap2019-08-191-0/+1
* | Merge pull request #735 from mahler/master•••Issue #651: Fix of typomattn2019-08-201-1/+1
|\ \ | |/ |/|
| * Issue #651: Fix of typo•••https://github.com/mattn/go-sqlite3/issues/651 =2019-08-191-1/+1
|/
* Merge pull request #732 from mattn/sqlite-amalgamation-3290000•••upgrade amalgamation codemattn2019-07-162-3109/+4059
|\
| * upgrade amalgamation codeYasuhiro Matsumoto2019-07-162-3109/+4059
|/
* Merge pull request #731 from Jason-Cooke/patch-1•••docs: fix typomattn2019-07-091-1/+1
|\
| * docs: fix typoJason Cooke2019-07-091-1/+1
|/