SaaSHub helps you find the best software and product alternatives Learn more →
Go-sqlite3 Alternatives
Similar projects and alternatives to go-sqlite3
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
PostgreSQL
Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
go-sqlite3 discussion
go-sqlite3 reviews and mentions
-
PSA: SQLite does not do checksums
My Go driver adds support for this by default, and I provide a simple(r) API to enable it.
https://github.com/ncruces/go-sqlite3/tree/main/vfs#checksum...
Weirdly, databases created with the macOS version of the sqlite3 CLI reserve 12 bytes, for some reason, so you can't ever enable checksums on those DBs.
-
Sqlite3 WebAssembly
For server side, you'll likely need a different build of Wasm SQLite, that handles concurrency (and file locking) differently.
Also, WASI is very far from answer (so far). The SQLite amalgamation builds fine for WASI but concurrency is an unsolved issue.
I had to build a VFS from scratch to get my Wasm based SQLite driver into a usable shape.
https://github.com/ncruces/go-sqlite3/blob/main/vfs/README.m...
-
Some Go web dev notes
https://github.com/bxcodec/dbresolver
> Also sometimes if I have two tables where I know I’ll never need to do a JOIN between them, I’ll just put them in separate databases so that I can connect to them independently.
If this data belongs together and you're just doing this to improve concurrency, this may be a case where `BEGIN CONCURRENT` helps.
https://sqlite.org/src/doc/begin-concurrent/doc/begin_concur...
If you want to experiment with `BEGIN CONCURRENT` you could do worse than try my Go SQLite driver:
https://github.com/ncruces/go-sqlite3
https://github.com/ncruces/go-sqlite3/tree/main/embed/bcw2
-
Show HN: Roast my SQLite encryption at-rest
Yep, I just made it tweakable at build, which was always the intent, although I expect the default to be popular.
https://github.com/ncruces/go-sqlite3/blob/67d859a5/vfs/adia...
That's unfortunate about the default parameters, but note that you can also replace the KDF altogether (besides just not using it).
You just need to implement this interface, with any HBSH construction and KDF:
https://github.com/ncruces/go-sqlite3/blob/67d859a5/vfs/adia...
If you keep the HBSH and change the KDF, your file format will be “compatible.”
-
Jsonfile: A Quick Hack for Tinkering
struggling figuring out how to make my cgo sqlite cross-compile to Windows
Plenty of people trying to fix that.
There's at least:
https://modernc.org/sqlite
Then there's https://github.com/zombiezen/go-sqlite that actually builds https://crawshaw.io/sqlite on top of modernc.
And there's mine that has both a low level and a database/sql driver builds and runs everywhere Go does: https://github.com/ncruces/go-sqlite3
-
SQLite-memory-vfs: Open a SQLite db from memory in Python, without hitting disk
If you're interested both SQLite's and my memdb VFSes implement safe locking.
Depending on your familiarity with Go, mine maybe easier to follow, or not.
https://github.com/ncruces/go-sqlite3/blob/f1b00a9944730eaa9...
-
Show HN: My Go SQLite driver did poorly on a benchmark, so I fixed it
One thing I tried to make sure, to avoid the pitfall modernc is having, is to make sure building "the WASM BLOB" is easily reproducible with widely available tools:
https://github.com/ncruces/go-sqlite3/blob/main/.github/work...
I do apply some light patches to SQLite, but so far they've always cleanly applied, and I can produce a new release within hours of being notified of SQLite releases.
- JSONB Has Landed in SQLite
- Show HN: Go bindings to SQLite using wazero
-
Show HN: Gogosseract, a Go Lib for CGo-Free Tesseract OCR via Wazero
Disclosure: I'm working on alternative Cgo-less bindings for SQLite, using wazero.
https://github.com/ncruces/go-sqlite3
One of the problems of the modernc approach (IMO) is that they're not just transpiring CPU/compute stuff, but entirely OS/platform stuff.
Each Go file of theirs is a xxx_os_arch.go that starts with 100s of OS-#defines-as-consts, and goes on to transpile fully #ifdefed code.
It also implements antithetical (in Go) stuff like goroutine local storage, because libc pthreads can't live without it.
And all IO is via direct syscalls that will never play nice with the Go scheduler, because, again this is OS level stuff.
WASM defines a cross platform CPU and an ABI, and using that for compute and the bottom OS layer in Go you get (IMO) a nicer end result.
Given the hard task of generating decent code from WASM at load time (wazero's compiler is pretty naive, a better one is being developed, but it will take seconds to generate good code for anything non trivial like SQLite) I wouldn't mind having a solution that translated to Go, or Go ASM, at build time.
-
A note from our sponsor - SaaSHub
www.saashub.com | 5 Dec 2024
Stats
ncruces/go-sqlite3 is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of go-sqlite3 is Go.