Turso is an in-process SQL database, compatible with SQLite
1–10 of 109 posts
Re: Turso is an in-process SQL database, compatible with SQLite
#2[dead]
Re: Turso is an in-process SQL database, compatible with SQLite
#3But I thought turso already had an SQLite-compatible thing, libsqlite!
Turns out this is covered in the readme: libsqlite is a fork (so, presumably C) while turso database is a rust rewrite.
Good luck to the friends at Turso!
Re: Turso is an in-process SQL database, compatible with SQLite
#4I'm confused why I would use this when Sqlite exists?
Being written in Rust it's not even a good libc-less drop in choice for a language like Go?
Re: Turso is an in-process SQL database, compatible with SQLite
#5I'm confused why I would use this when Sqlite exists? Being written in Rust it's not even a good libc-less drop in choice for a language like Go?
> Turso Database is a project to build the next evolution of SQLite in Rust, with a strong open contribution focus and features like native async support, vector search, and more
Re: Turso is an in-process SQL database, compatible with SQLite
#6I'm confused why I would use this when Sqlite exists? Being written in Rust it's not even a good libc-less drop in choice for a language like Go?
One quick thing I can think of is multiple writers [0]
[0]: https://turso.tech/blog/beyond-the-single-writer-limitation-...
Re: Turso is an in-process SQL database, compatible with SQLite
#7Turso is sqlite with a server client arch. I use them for stashing my llm usage logs all the time. Pretty neat. Plus I'm rooting for them to rewrite sqlite in Rust.
Re: Turso is an in-process SQL database, compatible with SQLite
#8I'm confused why I would use this when Sqlite exists? Being written in Rust it's not even a good libc-less drop in choice for a language like Go?
One quick thing I can think of is multiple writers [0] [0]: https://turso.tech/blog/beyond-the-single-writer-limitation-...
This is a huge differentiator. I built our internal meme platform with Turso. Really fun and easy to use.
Re: Turso is an in-process SQL database, compatible with SQLite
#9I'm confused why I would use this when Sqlite exists? Being written in Rust it's not even a good libc-less drop in choice for a language like Go?
One quick thing I can think of is multiple writers [0] [0]: https://turso.tech/blog/beyond-the-single-writer-limitation-...
isn't this just pushing the complexity around? Either my write thread manages the lock, or turso's does.
Re: Turso is an in-process SQL database, compatible with SQLite
#10I’d imagine there’s an extremely long tail of features and quirks that will take time to iron out even after SQL compatibility is achieved. Looks like it’s still missing some important features like savepoints (!!!), windows and attach database.
I’d be more excited and imagine it would be more marketable if it focused instead on being simply an embedded sql db that allowed multiple writers (for example), or some other use case where SQLite falls short. DuckDB is an example- SQLite but for olap.