Skip to content

Releases: OP-Engineering/op-sqlite

Release 11.2.13

06 Jan 08:20
f110a6d
Compare
Choose a tag to compare

What's Changed

Full Changelog: 11.2.12...11.2.13

Release 11.2.12

01 Jan 11:30
3ff2f7e
Compare
Choose a tag to compare

What's Changed

Full Changelog: 11.2.11...11.2.12

Release 11.2.11

31 Dec 08:16
6f426ef
Compare
Choose a tag to compare

What's Changed

Full Changelog: 11.2.10...11.2.11

Release 11.2.10

30 Dec 17:47
cdd3a65
Compare
Choose a tag to compare

What's Changed

  • Try to call realpath to resolve the correct location of the db by @ospfranco in #218

Full Changelog: 11.2.9...11.2.10

Release 11.2.9

30 Dec 10:50
e56ca63
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 11.2.8...11.2.9

Release 11.2.8

22 Dec 10:42
64846cf
Compare
Choose a tag to compare

What's Changed

Full Changelog: 11.2.7...11.2.8

Release 11.2.7

20 Dec 21:37
6b6790f
Compare
Choose a tag to compare

What's Changed

Full Changelog: 11.2.6...11.2.7

Release 11.2.6

20 Dec 15:43
48483f0
Compare
Choose a tag to compare

This is a big release! The threading model of the library has been changed to have only one of thread per connection. This will get rid of a lot of race conditions people have been encountering at the price of making the library a smidge slower, but correctness comes before speed.

You can now have multiple connections per database, which is how sqlite is meant to be used. You should have ONLY ONE write connection though, otherwise you might get issues still:

import {open} from "@op-engineering/op-sqlite"

let readConnection = open({name: "db.sqlite"})
let writeConnection = open({name: "db.sqlite"})

What's Changed

New Contributors

Full Changelog: 11.2.5...11.2.6

Release 11.2.5

18 Dec 13:45
Compare
Choose a tag to compare

Release 11.2.4

16 Dec 20:05
f630279
Compare
Choose a tag to compare

What's Changed

Full Changelog: 11.2.3...11.2.4