Pekka Enberg
Pekka Enberg
Maybe let's be as confusing as SQLite here
Hey @petersooley, could you please rebase this so we can get it merged?
Wow, nice, did not know about the project, thanks for the suggestion @nappa85!
That AI-generated solution looks like the kind of path to take! Of course, we should also switch to allocator-api2 which gives Zig-style explicit allocators.
The question on static allocation is interesting! I tend to think TigerBeetle's approach here is too extreme for my taste and that throwing away dynamic allocation makes the code too...
Hey @kaaax0815, this is still a bit early so let's just treat and merge #169 independently.
https://github.com/tursodatabase/limbo/issues/1283 might be related. My guess is that there's something broken with our `io_uring` backend (or the async execution model) compared to the synchronous, system call-based I/O we use on...
Lots of things changed in the b-tree code, closing for now.
@pedrocarlo Based on the feedback I've heard, people don't exactly love FTS5, but I don't claim to know for a fact what they want. Tantivy is just a suggestion from...
I am leaning towards shipping FTS first because it's what many applications expect.