We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think if we use fixed-size types, we'll save a u64 or u32 length. @cberner is this right?
So we can change our table definitions to:
const HEIGHT_TO_HASH: TableDefinition<u64, [u8; 32]> = TableDefinition::new("HEIGHT_TO_HASH"); const OUTPOINT_TO_ORDINAL_RANGES: TableDefinition<[u8; 36], [u8]> = TableDefinition::new("OUTPOINT_TO_ORDINAL_RANGES"); const OUTPOINT_TO_TXID: TableDefinition<[u8; 36], [u8; 32]> = TableDefinition::new("OUTPOINT_TO_TXID");
The text was updated successfully, but these errors were encountered:
Yep! You'll save a u32 length for every key and/or value
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I think if we use fixed-size types, we'll save a u64 or u32 length. @cberner is this right?
So we can change our table definitions to:
The text was updated successfully, but these errors were encountered: