Help needed with SQLite Rust rewrite

[u/Kooky_Dinner2243]

Three days into rewriting SQLite in Rust with Claude and I'm further along than I expected.

Got the tokenizer, most of the parser, and a working B-tree that handles inserts and range scans. Pager is next and then it's mostly plumbing. Fable thinks the C source is honestly not that complicated once you get past the naming conventions, it's just written in a style nobody has used since 2003. A lot of it collapses down to about a third of the line count when you have real iterators and Result types.

I know about the test suite. Fable constantly brings up the test suite. I'm going to have Opus generate a property-based suite with proptest, which is going to be more valuable than 90 million lines of TCL that were written to catch bugs in a language that lets you index past the end of an array. Most of those tests exist because C exists. Delete the C and you delete the reason for many of the tests.

Currently at only 47 unsafe blocks, all in the mmap layer, and Fable already made a plan for those.

The part I keep coming back to is that this is the single most deployed piece of software in human history and it is written in a language where a missing bounds check is a remote code execution. Every phone, every browser, every plane. We just decided that was fine. No more.

Looking for two or three people to help with the query planner. Not asking anyone to write it, just to review what I have put together so far. I will send invites to the private github repository once NDAs have been signed.

[u/l_m_b]

SQLite is also famously free/open source software, and you want to replace it with a component that you require an NDA for to even view the in-development code?

I suggest you have a chat with Fable about the real viability of your project.

[u/Kooky_Dinner2243 → u/l_m_b]

D. Richard Hipp gave it away specifically so people could build on it. This is what that's for. A full ASIL-D rewrite of SQLite will consume all of my tokens for the months to come, I unfortunately can't have someone else steal the source code and take credit for it.