sqlite: A CGo-free port of SQLite/SQLite3

pstuart

So is this a handmade port vs the translated port done by modernc?

yodon

Seems like there are some trademark issues with just calling this SQLite.

jsherer

I was confused a few weeks ago. Check out the go pkg: https://pkg.go.dev/modernc.org/sqlite 1. gitlab.com/cznic/sqlite is the primary repo 2. github.com/cznic/sqlite was the github mirror but it moved 3. github.com/mordernc-org/sqlite is the read-only mirror of the primary repo Cheers!

ftgffsdddr

Gitlab requires js Would you please host it on a different forge, eg codeberg

usrnm

The readme really lacks the answer to the "why" question. What's the use case, why should I prefer it over real sqlite?

ncruces

There's also my take on this [1], which does machine translation from C to Go via Wasm using [2]. It's a somewhat less faithful translation, since I manually ported the VFS (SQLite OS abstraction layer). OTOH, each SQLite connection is sandboxed (can't access/corrupt Go memory, or other SQLite connections). And it should run everywhere Go runs. 1: https://github.com/ncruces/go-sqlite3 2: https://github.com/ncruces/wasm2go