go-database-sql-tutorial VS go-sqlite3

I don't understand why modern project managers bite into object-oriented reading from relational databases like a dog to a bone. After all, SQL was created for processing relational databases, and attempts to bypass this language only lead to wasted resources and eerily slow queries. I had to fix a lot of such "pearls" made with Entity Framework (.NET/C#). Analogue GO language tools are no better. Use the GO language package dabase/sql, which is not only fast and easy, but also has an excellent tutorial (http://go-database-sql.org/).

I study database/sql using https://go-database-sql.org guide. At the time, I’m interested in prepared statements.

My advice I think would be to try and break this down into stages. First of all I think you need to get comfortable with how to work with a database from Go, so separately from your main application just create a new throwaway folder and start messing about with connecting and then inserting/retrieving data. This site has some good basic info about that part of things: http://go-database-sql.org/

I highly recommend to work yourself through this tutorial on how to properly use database/sql package.

Go database/sql tutorial is the de-facto resource for understanding how to work with this package together with examples using MySQL and PostgreSQL.

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

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...

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.

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.

The github.com/ncruces/go-sqlite3 is a link.

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).