Create B+ Tree indexed database implementation

[maxfierrog]

Multi-table, single-file database that supports concurrent and isolated transactions on different tables.

See design document: https://docs.google.com/document/d/1VFVDdnb-YiU1K4mhw3I2vw4c6dSlKFYFfK-pP5ONVzc

Recommended Courses (UC Berkeley)

If you can't tell whether this is out of your scope, we recommend the following experience:

• CS 61B (minimum)
• CS 61C (minimum)
• CS 186
• CS 162

[BnjmnZmmrmn]

can i be assigned & get permissions to link a pr

[BnjmnZmmrmn]

https://github.com/nimrodshn/btree - stale (maybe?) project for bplus tree written in rust, might contain useful info

[maxfierrog]

https://github.com/nimrodshn/btree - stale (maybe?) project for bplus tree written in rust, might contain useful info

Great find, looking at their repo makes me feel like this is super achievable in a semester or two.

[BnjmnZmmrmn]

how can link pr that doesnt necessarily close issue, just progresses it? or does closing issue happen manually after pr merge

[maxfierrog]

The semantics around issues, PRs, and branches are pretty weird. There is no way to do what we want here. Let's keep a 1 : 1 relationship between issues and PRs, and have potentially many sub-branches that work on different things on the PR.

For example, let's call the PR that solves this issue "B+ Tree Index Implementation," and keep using dev-bplusdb as its corresponding branch. We can then make sub-branches if we want to have that notion of gradual progress.

Speaking of, let's all carry out development on dev-bplusdb without forking the repo. Of course it's fine to fork it for self-experimentation, but working on the on-repo branch makes it easier to collaborate.

Lmk if questions / concerns

[BnjmnZmmrmn]

sg for most part
wrt to development i feel forking allows for review of individual contributions to dev-bplusdb. can i still create prs as i did for the skeleton, or would u rather i just push to dev-bplusdb without review @maxfierrog

[BnjmnZmmrmn]

skeleton created - #35

[maxfierrog]

sg for most part wrt to development i feel forking allows for review of individual contributions to dev-bplusdb. can i still create prs as i did for the skeleton, or would u rather i just push to dev-bplusdb without review @maxfierrog

that makes sense, i do appreciate that aspect of forking

feel free to do what works best for you (PR to dev-bplusdb either from your fork or from a sub-branch you create on this repo). feel free to also push to it without review as you see fit -- i only really want to review changes on dev (that being said, reviewing significant changes made to dev-bplusdb will make that a lot easier down the road)

ultimately it's subjective ofc, but i'm always willing to do reviews, and i totally trust your judgement wrt what is most efficient in terms of productivity

[BnjmnZmmrmn]

sg thanks max!

[BnjmnZmmrmn]

bplustree api skeleton - #36

[maxfierrog]

Created high-level design document outlining testable modules:

https://docs.google.com/document/d/1VFVDdnb-YiU1K4mhw3I2vw4c6dSlKFYFfK-pP5ONVzc