go-sqlite VS Sqinn-Go

Check out https://github.com/zombiezen/go-sqlite if you're interested in trying out Sqlite in Go again. Nice interface, negligible compile time impact, fast, compiles without CGO. It's very comfortable.

I agree that going from text to sqlite is a bit of a hurdle, especially if you're not writing C :)

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

There are several different Go bindings for SQLite. I maintain https://pkg.go.dev/zombiezen.com/go/sqlite

I like and use https://github.com/zombiezen/go-sqlite for CGo-free SQLite. It avoids some of the problems database/sql has, discussed here: https://crawshaw.io/blog/go-and-sqlite.

> C libraries are required to interact with SQLite

Or: modernc.org/sqlite (https://github.com/zombiezen/go-sqlite), "an automatically generated translation of the original C source code of SQLite into Go"

https://pkg.go.dev/modernc.org/sqlite via https://pkg.go.dev/zombiezen.com/go/sqlite

modernc.org/sqlite provides a database/sql driver, but does not (currently) provide an easy way to get at the more advanced functionality of SQLite, like streaming blob I/O or user-defined functions. David Crawshaw has argued that the database/sql API is not a good fit for SQLite, which is how crawshaw.io/sqlite came about.

Note that Squinn is not "native go" or "go only", but the owner insists on misleading people:

https://github.com/cvilsmeier/sqinn-go/issues/8

If you want to avoid cgo, consider sqinn as well: benchmarks.

Of course, it may seem... odd to add a remote interface to an embedded database, but I think that it fits some niches well, especially when decoupling persistence and logic is needed, without renouncing to the expressivity of SQL. It was inspired by PostgREST, but it’s much more “low level” – and it should be even simpler to adapt to some cases. Also, it serves the same purpose of sqinn but with a more general interface.

Why don't you try a pure-Go implementation? Should have enough features implemented for basic use

https://github.com/cvilsmeier/sqinn-go