tursodatabase/turso

…er customer (organization). Of course more of everything is manual but it’s not as hard as you’d expect if you build for it. https://rivet.dev/blog/2025-02-16-sqlite-on-the-server-is-misunderstood/ If you need sqlite over the network you can look at https://turso.tech/ it’s a almost drop in replacement for sqlite ( https://github.com/tursodatabase/turso/blob/main/COMPAT.md )

I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing

They're not aiming at replacing SQLite-in-C with SQLite-in-Rust, they're doing this so they can implement more additional functionality faster than with C's chainsaw-juggling-act semantics and the inability to access the proprietary SQLite test suite. See the features and roadmap at https://github.com/tursodatabase/turso

Like this? https://github.com/tursodatabase/turso Disclaimer: Credit goes to whoever mentioned this in this discussion before me.

SQLite's test suite is proprietary. A Rust implementation exists. It's called turso https://github.com/tursodatabase/turso There's a whole company around it.

I forgot what Limbo was, Rust rewrite of SQLite, now called Turso. https://github.com/tursodatabase/turso I could see it being useful for pure Rust projects once its completed. I mean in Java / Kotlin land, I prefer to use H2 in some cases over SQLite since its native to the platform and H2 is kind of nice altogether. I could see myself only using this in Rust in place of SQLite if its easy to integrate and use on the fly.

In the same area, I am tracking the Rust rewrite of sqlite by Turso [1]. The big advantage is the file format compatibility. [1] https://github.com/tursodatabase/turso

fwiw there's a project doing just that: https://github.com/tursodatabase/turso they have a blog hinting at some answers as to "why": https://turso.tech/blog/introducing-limbo-a-complete-rewrite-of-sqlite-in-rust

This is ignoring the elephant in the room: SQLite is being rewritten in Rust and it's going quite well. https://github.com/tursodatabase/turso It has async I/O support on Linux with io_uring, vector support, BEGIN CONCURRENT for improved write throughput using multi-version concurrency control (MVCC), Encryption at rest, incremental computation using DBSP for incremental view maintenance and query subscriptions. Time will tell, but this may well be the future of SQLite.

I am not sad about rewriting sqlite in Rust because this is the third such attempt I've seen, and just like the other two it looks like this project is totally doomed: https://github.com/tursodatabase/turso/ Like, look: https://github.com/tursodatabase/turso/issues/6412 It's stunning considering this project is advertised as a beta. There are hundreds of bugs like this. It's AI slop that gets worse the more AI is thrown at it. SDL is 100% correct to keep this AI mess as far away from their project as possible.

…es a data-corrupting bug, there's a regression test, good (although the original bug sounds like it should've been caught by a suite like the one SQLite has) That's just a couple days worth of PRs. This style of development does not inspire confidence. They develop features, sure. But I want my database to be rock-solid and completely covered by tests, not just move fast and break things. It's not FUD to just look at how they approach PRs.

…, I don't buy it. C is like JavaScript, it's not perfect, is everywhere and you cannot replace it without a lot of effort and bugfix/regression tests. If I take for example sqlite (25 years old [3]) there are already 2 rewrites in rust [1] and [2], and each one has its bugs. And as an end user I'm more enclined to trust the battle-tested original for my prod than its copies. As long as I don't have the proof the rewrite is at least as good as the original, I'll stay with the original. Simple equals more maintainable. That's also why sqlite maintainers won't rewrite it in any other language [4]. The trade of rust is "you can lose features and have unexpected bugs like any other language, b…

… strive to foster a community that values diversity, equity, and inclusion. We encourage others to speak up if they feel uncomfortable. Sometime after the HN backlash[2], that paragraph was removed. Eventually, Turso released https://github.com/tursodatabase/turso without a code of conduct and hasn't had one since. For me, the saddest part of the affair is that Richard Hipp and Glauber are both committed Christians. There should be no reason for envy, enmity, or memory games. But when business and money was on the table, it seems only one of them followed Jesus. [1] https://github.com/tursodatabase/libsql/commit/3ac3ad263c0f09284d85bc74db0c31e322ffb8af https://web.archive.org/web/20221004…

3 different types of sqlite, 14 different versions total: https://github.com/tursodatabase/turso/network/dependencies?q=sqlite