the monkeys demand a dbms
Find a file
2026-05-27 08:19:12 -04:00
src clean 2026-05-27 08:19:12 -04:00
.gitignore gitignore 2026-05-05 16:28:45 -04:00
Cargo.lock O_DIRECT 2026-05-04 11:53:24 -04:00
Cargo.toml O_DIRECT 2026-05-04 11:53:24 -04:00
cows.png LOTS OF STUFF 2026-04-11 00:37:25 -04:00
LICENSE LOTS OF STUFF 2026-04-11 00:37:25 -04:00
README.md Update README.md 2026-04-26 15:40:19 -04:00
rustfmt.toml clean up writetx 2026-04-27 23:55:40 -04:00

MOOODB

Cow

we strictly follow the 1 M and 3 Os of MOOODB:

  1. [M]akes a new subtree on writes!
  2. [O]n disk!
  3. [O]rchestrates transactions!
  4. [O]nly a fool would not believe in MOOODB!

are your btrees imoootable?


MOOODB is a copy-on-write, B+tree based relational database system, and is a work in progress.

  • Single writer, multiple reader - reads are not blocked by the writer.
  • Durability is provided by copy-on-write, and readers see the most recent version of the DB until the current writer commits.
  • In the event of a mid-tx crash, the most recent version of the DB will be intact.
  • Uses B+trees for indicies and freelist, with heap pages for actual tuples (with the exception of covering indicies, like for the freelist).
  • Storage engine is close to being in working order, then work will start on query planning & execution.