A CGo-free port of SQLite/SQLite3

#1

Post by tosh » Sun, Jun 07, 2026, 1:53 PM UTC

Re: A CGo-free port of SQLite/SQLite3

#2

Post by pstuart » Sun, Jun 07, 2026, 6:47 PM UTC

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

#3

Post by yodon » Sun, Jun 07, 2026, 6:49 PM UTC

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

#4

Post by vicek22 » Sun, Jun 07, 2026, 6:59 PM UTC

pstuart wrote: post #2

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

modernc is the name of the GitHub fork (identical repo) of the same project. This is machine translated, not hand written.

#5

Post by jsherer » Sun, Jun 07, 2026, 7:22 PM UTC

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!

#6

Post by downrightmike » Sun, Jun 07, 2026, 7:26 PM UTC

yodon wrote: post #3

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

SQL would have been SEQL if not for trademark issues, the torch is passed

#7

Post by ftgffsdddr » Sun, Jun 07, 2026, 7:36 PM UTC

[flagged]

#8

Post by slopinthebag » Sun, Jun 07, 2026, 7:41 PM UTC

ftgffsdddr wrote: post #7

[flagged]

[flagged]

#9

Post by usrnm » Sun, Jun 07, 2026, 7:48 PM UTC

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

#10

Post by blubber » Sun, Jun 07, 2026, 8:05 PM UTC

usrnm wrote: post #9

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

Because it's cgo-free maybe?