Build your own SQLite in Rust, Part 5: Evaluating queries
blog.sylver.dev
Build your own SQLite in Rust, Part 5: Evaluating queries
1–10 of 28 posts
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#2Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#3This is a really cool set of articles, and while it’s not going to replace sqlite it’s fantastic to see the pieces needed to do sql with SQLite’s file format
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#4This is a really cool set of articles, and while it’s not going to replace sqlite it’s fantastic to see the pieces needed to do sql with SQLite’s file format
SQLites alternative in rust is a thing though https://github.com/tursodatabase/limbo
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#5Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#6This is a really cool set of articles, and while it’s not going to replace sqlite it’s fantastic to see the pieces needed to do sql with SQLite’s file format
SQLites alternative in rust is a thing though https://github.com/tursodatabase/limbo
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#7Making a basic database that works is not hard, but making a robust one is really hard. What makes SQLite shines is its extensive testsuite. I still don't understand the motivation of limbo, as without years of hardwork on test you can't say you are correct, and why i should pay for it...
But the years of work put into the existing project to make it robust don't mean the exact same years have to be spent on the reimplementation:
- there's been work spent on discovering the right architecture and evolving the db format. A new impl can copy the end result.
- hard lessons have been learned about dealing with bad disks, filesystems, fsync, flaky locks, etc. A new impl can learn from the solutions without having to rediscover them the hard way.
- C projects spend some time on compatibility with C compilers, OSes, and tweaking build scripts, which are relatively easy in Rust.
Testing will need a clever solution. Maybe they'll buy access to the official test suite? Maybe they'll use the original SQLite to fuzz and compare results?
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#8Earlier quoted context omitted.
SQLites alternative in rust is a thing though https://github.com/tursodatabase/limbo
Can't wait to get my Blazingly Fast™ Managed Cloud SQLite for only 0.0001$ per virtual compute second.
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#9Making a basic database that works is not hard, but making a robust one is really hard. What makes SQLite shines is its extensive testsuite. I still don't understand the motivation of limbo, as without years of hardwork on test you can't say you are correct, and why i should pay for it...
It's up to the developers to decide if the outcome is worth the effort.
Maybe they're right, maybe they're wrong, but either way – if they succeed, we're all better off for it, aren't we?
Re: Build your own SQLite in Rust, Part 5: Evaluating queries
#10Earlier quoted context omitted.
Can't wait to get my Blazingly Fast™ Managed Cloud SQLite for only 0.0001$ per virtual compute second.
I think you’re looking for LiteFS https://fly.io/blog/introducing-litefs/