44e47686ee
Tests that demonstrate current isolation behavior
3 years ago
a4c4374daf
Update CHANGELOG
3 years ago
3907132761
Add detailed SQLite memstats to status/
3 years ago
aa8df67592
DB-level unit tests pass
3 years ago
161abb094d
Add db-level FK constraints unit test
3 years ago
deb4dabf2e
Thread through foreign key constraint controls
3 years ago
2cad491f40
Better creation of SQLite DSNs
3 years ago
f7b390ab28
Adding JSON1 unit test
3 years ago
96f9e85ee3
More concurrent query testing
3 years ago
3cee11de6f
Count number of query errors
3 years ago
6c69e8a9b5
Upgrade to new compile options
3 years ago
ea723ee830
Ping databases on open to ensure full availability
3 years ago
953e82f7c4
Add SQLite compile-time options to status output
3 years ago
11da97f455
Fix typo
3 years ago
497d3dd873
Remove obsolete foreign key constraint control
3 years ago
c086eba427
Remove debug statement
3 years ago
b83424484d
Enhance SQLite database status
3 years ago
cc8b924e64
Fix WaitGroup usage in test
3 years ago
4f2818d037
Add concurrent query test
3 years ago
eec7494d62
DB size requires a read-write connection
3 years ago
6edff5ba24
Deal with SQLite connection "caching"?
...
https://github.com/mattn/go-sqlite3/issues/966
3 years ago
bf51947ca9
Better error messages
3 years ago
d101e10469
Test writing via the query connection
...
It should fail.
3 years ago
854cf362fd
Don't specify mode=rw on file open
...
Not sure why.
3 years ago
6dc9583dab
Implement concurrent reads and writes
...
Disk doesn't support it yet, as it has not moved to WAL mode. Perhaps
wait for next release to do that.
3 years ago
db1768c63f
Initial implementation of two database connections
3 years ago
90a0d397c6
Switch from mode=memory to vfs=memdb for in-mem DB
3 years ago
791a1b0b72
Remove obsolete references to DSN
3 years ago
e0da96dd55
Remove support for specifying SQLite DSN
...
This is a breaking change. However this feature hasn't been tested and
allows end-users to break the system too easily. Low-level control over
the SQLite database is better done with PRAGMA commands where possible.
3 years ago
2924ed407d
Upgrade to rqlite/go-sqlite3 v1.20.4
3 years ago
028419af0f
Fix race in in-memory database testing
3 years ago
1ee7a9eb17
Limit in-memory connection pool to 1 connection
...
https://github.com/mattn/go-sqlite3/issues/959#issuecomment-890283264
3 years ago
911df4c03b
Don't leak a database if deserialization fails
...
Fixes https://github.com/rqlite/rqlite/issues/837 .
3 years ago
8693694d14
Add current SQLite journal mode to status output
3 years ago
503825dbaf
Remove Abort functionality
...
No longer relevant since each Exec and Query gets its own connection.
3 years ago
561bb47a14
Port DB layer to sql/database
...
Empty statements now cause panic.
3 years ago
eb8dcf74ff
Start moving to SQL layer
...
Builds.
3 years ago
5f5f7dbbea
Sync use of DB connection
...
Possible, albeit simple, fix for https://github.com/rqlite/rqlite/issues/830
3 years ago
c5e67a548c
Even more records during db test
4 years ago
665d9913bb
Add top-level Deserialize() to db layer
4 years ago
b83b2b241d
Merge branch 'master' into no-disk-during-restore
4 years ago
18a4f38701
Add Copy() method to db layer
4 years ago
ce7a3a6912
Merge branch 'master' into no-disk-during-restore
4 years ago
535d690d7c
Tigthen up Store-level locking
...
Previous locking didn't look quite correct, and with the advent of the
Serialize functionality, it needs to be more precise.
4 years ago
7900adbf53
Add Deserialize to DB layer
4 years ago
9210297413
Unit test DB serialize
4 years ago
93a78f09a0
Add call to Serialize function
4 years ago
488a9554ea
Switch to rqlite fork of go-sqlite3
4 years ago
011bc00784
Add SQLite database page-centric size to status output
4 years ago
6575de779d
Use Protobuf for encoding Raft Log commands
...
This PR changes Raft Log Entry encoding from JSON to Protobuf. Furthermore, larger Raft commands (which can result from batching SQL statements, or individually long SQL statements) are compressed before encoding.
This primary reason for this change is to reduce IO load since that is one of the largest performance bottlenecks. It will also reduce internode traffic.
Legacy JSON-encoded commands are still handled by this code, so this change is backwards-compatible with previous releases in the v5 series.
4 years ago
Philip O'Toole