A pure Go embedded SQL database

Post by benhoyt » Sat, Jan 29, 2022, 11:38 PM UTC

eatonphil wrote: post #11

benhoyt wrote: post #9

Earlier quoted context omitted.

The same author ("cznic") has also built a C-to-Go compiler/transpiler and used it to convert SQLite to pure Go source, so that it doesn't require CGo: https://gitlab.com/cznic/sqlite ... the converted Go code is pretty much unreadable and it's somewhat slower than SQLite via CGo. But a pretty neat idea! I use it in one of my projects and it works well.

I saw that recently. I would be interested in using it but it wasn't clear what level of compatibility it has or how many tests it's passing/not passing.

Post by bbss » Sat, Jan 29, 2022, 11:45 PM UTC

benhoyt wrote: post #10

bbss wrote: post #6

Earlier quoted context omitted.

There are a few go libs now that offer SQLite without cgo. https://github.com/crawshaw/sqlite https://github.com/zombiezen/go-sqlite

crawshaw/sqlite actually uses CGo -- it's a wrapper around the C version of SQLite. For example, see https://github.com/crawshaw/sqlite/blob/23d646f8ac00d9dd2390... zombiezen/go-sqlite uses cznic's pure Go converted version of SQLite, so avoids CGo. It's explicitly stated to be "a fork of crawshaw.io/sqlite that uses modernc.org/sqlite, a CGo-free SQLite package. It aims to be a mostly drop-in replacement for crawsha…

Post by eatonphil » Sat, Jan 29, 2022, 11:45 PM UTC

benhoyt wrote: post #15

eatonphil wrote: post #13

Earlier quoted context omitted.

Wow! I'd almost trust it more if only 99% of tests were passing rather than 100% of tests passing. :)

Hehe. Well, if you look at the previous release it shows 99.7% percent of (a smaller number of) the tests passing. So you've got the best of both worlds. :-)

Post by vbitz » Sun, Jan 30, 2022, 12:10 AM UTC

anderspitman wrote: post #5

eatonphil wrote: post #4

Earlier quoted context omitted.

Well for one, if it's in Go, it wouldn't need Cgo.

It's pretty easy to statically link SQLite[0]. Are there other disadvantages to CGO? [0]: https://www.arp242.net/static-go.html

Post by throwaway894345 » Sun, Jan 30, 2022, 12:36 AM UTC

eloff wrote: post #17

christophilus wrote: post #7

Earlier quoted context omitted.

Yes. It doesn’t play nice with goroutines and Go’s concurrency model, from what I understand.

Yes, function calls across the boundary are slow. It's fine if the functions do lots of work, it's very expensive for function calls that should be cheap. For sqlite it might not matter too much, since any query does quite a bit of work.