35cf400919
fix tests
2016-12-09 12:58:20 +09:00
a160bbbc09
fix tree for tools/upgrade.go
...
Close #361
2016-12-09 09:08:59 +09:00
8ecd77c707
fix test
...
see https://github.com/golang/go/issues/18099
2016-12-01 12:12:18 +09:00
fba66eb116
Merge pull request #356 from gconnell/import
...
Fix example import to point to mattn repo.
2016-11-12 01:58:19 +09:00
341bfcf7f1
Fix example import to point to mattn repo.
2016-11-11 09:50:05 -07:00
ca5e381972
upgrade amalgamation code
2016-11-11 09:01:23 +09:00
f043f8092b
use prepare instead of Prepare
2016-11-09 01:13:34 +09:00
599dd7631f
disable combination of libsqlite3 and trace because travis(trusty) is too old.
2016-11-08 18:27:48 +09:00
6e9298a6b1
fix .travis.yml
2016-11-08 17:55:41 +09:00
aa33ddc53b
fix build
2016-11-08 17:24:01 +09:00
d1009b4fa6
fix build
2016-11-08 17:12:03 +09:00
bfeda3f4f6
fix build
2016-11-08 17:07:52 +09:00
14e5ed1773
Merge pull request #353 from fancycode/travis_tags
...
Test different build configurations on Travis.
2016-11-08 16:47:13 +09:00
2a8baa5914
Test different build configurations on Travis.
2016-11-08 08:40:35 +01:00
ea2afbe9e8
revert Multiple Result Set
2016-11-08 13:22:46 +09:00
dc448a0cb6
fix trace callback.
2016-11-08 12:27:31 +09:00
dd2c82226b
fix trace callback.
...
Close #352
2016-11-08 12:19:51 +09:00
3e26a9df84
Merge pull request #351 from andrefsp/data-race-fix
...
Fix data race introduced on 605d9d08
2016-11-08 01:07:26 +09:00
6c0a6bb9cd
Fix data race introduced on 605d9d08
...
This commit will fix a data race introduced on 605d9d08
2016-11-07 11:57:52 +00:00
51f43971ab
Merge branch 'master' of https://github.com/mattn/go-sqlite3
2016-11-07 16:16:47 +09:00
8d7068003b
FAQ about concurrency. Close #350
2016-11-07 16:16:17 +09:00
deed33aec7
cancel
2016-11-06 20:46:27 +09:00
605d9d0851
cancel
2016-11-06 20:43:53 +09:00
15491aeb9c
go vet && golint
2016-11-06 13:16:38 +09:00
cde7293c72
go vet && golint
2016-11-05 00:46:04 +09:00
0d1d1a644e
go vet && golint
2016-11-05 00:40:06 +09:00
a9ad8a09c9
remove trailing space
2016-11-05 00:28:43 +09:00
f4e49e6484
Merge pull request #348 from mattn/ping
...
new go1.8 feature
2016-11-04 23:24:02 +09:00
57eaf4c070
separate test
2016-11-04 15:17:21 +09:00
755d5be32c
add BeginContext
2016-11-04 15:15:16 +09:00
025b917610
add PrepareContext
2016-11-04 15:11:24 +09:00
29b191f206
build tag
2016-11-04 15:07:51 +09:00
4d2dc45165
Merge branch 'type' into ping
2016-11-04 15:05:42 +09:00
b23526fb3c
support named params
2016-11-04 15:00:29 +09:00
c95a77965c
context features
2016-11-04 14:24:22 +09:00
d0e4959926
add go18 new feature
2016-11-04 00:03:16 +09:00
6796d46c3a
implement go18 Pinger
2016-11-03 23:05:34 +09:00
86681de00a
remove -Wno-c99-extension
...
Close #343
2016-10-28 23:22:18 +09:00
dbe15b0408
Merge pull request #339 from brauner/2016-10-17/fix_libsqlite3_build
...
actually link to <sqlite3.h> when -tags libsqlite3
2016-10-28 17:48:50 +09:00
420dc664ed
upgrade: add ifdefines
...
This makes it possible to correctly link against the system sqlite. Also, don't
use defers with log.Fatal() since they won't be run on exit.
Signed-off-by: Christian Brauner <christian.brauner@canonical.com>
2016-10-28 10:28:19 +02:00
f6e7921d24
actually link to <sqlite3.h> when -tags libsqlite3
...
Building with -tags libsqlite3 used the sqlite3.h from the system but the go
compiler will compile all *.{c,h} files in the same direcory:
"When the Go tool sees that one or more Go files use the special import
"C", it will look for other non-Go files in the directory and compile
them as part of the Go package. Any .c, .s, or .S files will be compiled
with the C compiler." (https://golang.org/cmd/cgo/ )
So if users actually want to link against the system sqlite3 we should make
sqlite3-binding.* a noop.
Signed-off-by: Christian Brauner <christian.brauner@canonical.com>
2016-10-28 10:28:17 +02:00
955dae4ebd
Merge pull request #345 from joeshaw/backup-finalizer-fix
...
fix double free in SQLiteBackup.Close() on error
2016-10-28 08:55:17 +09:00
bdab31cc98
fix double free in SQLiteBackup.Close() on error
...
The sqlite3_backup_finish() function never fails, it just returns the
error code from previous operations. Previously if it returned an
error, the finalizer wouldn't be unset and sqlite3_backup_finish() would
be run again on an already-finished backup. This results in a
double-free and often segfaults.
The error handling is described in more detail in the "Error handling"
section of https://www.sqlite.org/backup.html .
2016-10-27 16:44:56 -07:00
e5a3c16c5c
Merge pull request #333 from nyarly/master
...
Added CFLAG config to ignore deprecations
2016-10-05 01:01:36 +09:00
61c9552d18
Added CFLAG config to ignore deprecations
2016-10-04 16:51:54 +01:00
4b0af852c1
Merge pull request #331 from a-p-/test-backup-error
...
Test the error reporting when preparing to perform a backup.
2016-09-27 11:28:46 +09:00
0e686cadf6
Test the error reporting when preparing to perform a backup.
2016-09-23 08:41:32 -04:00
3fb7a0e792
TestAggregatorRegistration may fail if trace feature is not implemented
2016-09-08 01:20:43 +09:00
0cc5236296
add tracecallback_noimpl.go
2016-09-08 01:13:15 +09:00
e63ddcaa1a
wrapper is not needress when not use libsqlite3
2016-09-08 01:00:36 +09:00
Yasuhiro Matsumoto