-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core/btree: small refactoring + documentation tweaks #543
Open
jussisaurio
wants to merge
4
commits into
main
Choose a base branch
from
btree-cell-doc-tweaks
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+104
−72
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
91cca0d
use more descriptive names in BTreeCursor::insert_into_cell()
jussisaurio c6b7ddf
Improve comments in BTreeCursor::compute_free_space()
jussisaurio 25338b5
refactor compute_free_space()
jussisaurio 42ea904
rename cell_get_raw_pointer_region() and refactor a bit
jussisaurio File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a bug? doesn't include
offset
for 1st page in db (which is 100 bytes, due to the database header)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm feels like it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually this one in particular probably isn't, because
PageContent
generally tries to hide the existence of the potential 100 byte offset from the user -- all of the read/write functions e.g.read_u16()
add the offset under the hood:whereas this quoted code does the following:
so the offset actually MUST not be added here because then it would be double-added :)
there might be a way to refactor this to make it less footgun-y
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I'm blindly guessing that your thought process when naming
pub fn cell_get_raw_pointer_region()
was that 'raw' means that it includes the offsetThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still thinking there is a 100-byte offset related error somewhere that is causing CREATE TABLE errors