Skip to content
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

Use integer ids for Sqlite bidirectional index #1599

Merged
merged 1 commit into from
Jan 3, 2024
Merged

Conversation

werkt
Copy link
Collaborator

@werkt werkt commented Jan 3, 2024

The cost in size for a single table bidirectional index is vast compared to the use of 3nf integer keys. Experimental estimates offer a decrease in file size of 90%.

The cost in size for a single table bidirectional index is vast compared
to the use of 3nf integer keys. Experimental estimates offer a decrease
in file size of 90%.
@werkt werkt merged commit 413021d into bazelbuild:main Jan 3, 2024
2 checks passed
@werkt werkt deleted the sqlite branch January 3, 2024 14:52
werkt added a commit to werkt/bazel-buildfarm that referenced this pull request Jan 4, 2024
werkt added a commit to werkt/bazel-buildfarm that referenced this pull request Jan 4, 2024
werkt added a commit that referenced this pull request Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant