sqinn
go-sqlite3
sqinn | go-sqlite3 | |
---|---|---|
4 | 22 | |
74 | 271 | |
- | - | |
7.0 | 9.5 | |
about 1 month ago | 5 days ago | |
C | Go | |
The Unlicense | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sqinn
-
Show HN: My Go SQLite driver did poorly on a benchmark, so I fixed it
First part of the README that hasn't changed in 2 months:
> Sqinn-Go is a Go (Golang) library for accessing SQLite databases without cgo. It uses Sqinn https://github.com/cvilsmeier/sqinn under the hood. It starts Sqinn as a child process (os/exec) and communicates with Sqinn over stdin/stdout/stderr. The Sqinn child process then does the SQLite work.
> If you want SQLite but do not want cgo, Sqinn-Go can be a solution.
This seems pretty clear to me about what's happening. It makes an OS call to a third-party executable (sqinn), pipes the result from stdout back into the Go code. The advantage is you don't have to compile the C code alongside your Go code.
Honestly, I don't really know how much more clear the author could be. I guess if you don't know what stdin, stdout, and stderr are it might be confusing? It's hard to imagine that a programmer who is interested in this library isn't familiar with those concepts though.
- Show HN: Sqinn-Go is a Golang library for accessing SQLite databases in pure Go
-
SQLite in Go, with and Without Cgo
I've not used it, but sqinn is one sqlite server meant specifically to be used by languages without c calling conventions:
https://github.com/cvilsmeier/sqinn
-
SQLite in Go, with and without cgo
The latest supported version is 3.38.3: https://github.com/cvilsmeier/sqinn/releases/tag/v1.1.15
go-sqlite3
- Show HN: Roast my SQLite encryption at-rest
-
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.
- Show HN: Sqinn-Go is a Golang library for accessing SQLite databases in pure Go
-
Go bindings to SQLite using Wazero
The github.com/ncruces/go-sqlite3 is a link.
-
C to WASM to Go
Using the stack pointer global is an interesting hack. I'd never thought of that. Need to compare with what I'm doing for SQLite (a kind of per connection arena).
What are some alternatives?
tcl
xcgo - Golang cross-platform builder docker image with CGo and other tooling
drydock - Experiment in unit testing with PostgreSQL using Docker
zenity - Zenity dialogs for Golang, Windows, macOS
sqlite
go-sqlite3 - sqlite3 driver for go using database/sql
Sqinn-Go - Golang SQLite without cgo
go-sqlite - pure-Go SQLite driver for Go (SQLite embedded)
homebrew-musl-cross - Homebrew Formula for static-friendly musl-based GCC macOS-to-Linux cross-compilers
acmd - Simple, useful and opinionated CLI package in Go.
venomoid - Defanging viper