feat(storage): make custom table INSERT incremental #6
Merged
Conversation
Adds Callout/Embed/WikiLink node variants. Map them to skipped nodes in node_to_parts, same as Fragment/Empty, to keep the match exhaustive.
Previously every INSERT INTO rewrote a table's full row history inline in the catalog, making insert cost grow with total table size. Rows now live in their own append-only page chain (mirroring document blocks), so INSERT only writes the new rows plus a small fixed-size catalog update instead of re-serializing everything already on disk. Bumps the on-disk format to FILE_VERSION 3 (breaking change for existing .mq-db files).
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.