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
BonsaiStorageError
Bonsai-trie version: 322af3f
Current behavior:
Double insertion of the same key into a bonsai db without calling commit between insertions results in BonsaiStorageError::Trie("Couldn't fetch node in db").
commit
BonsaiStorageError::Trie("Couldn't fetch node in db")
According to @AurelienFT this could be due to the db trying to access the key to replace it while it hasn't yet been committed to storage.
Expected behavior:
Bonsai db should be able to handle double insertions without having to commit to storage.
Steps to reproduce:
Perform double insertion of the same key into a bonsai db in a single commit.
Related code:
The function currently crashing: preload_node_subtree
preload_node_subtree
The text was updated successfully, but these errors were encountered:
Fixed by #20
Sorry, something went wrong.
AurelienFT
No branches or pull requests
Bug Report
Bonsai-trie version: 322af3f
Current behavior:
Double insertion of the same key into a bonsai db without calling
commit
between insertions results inBonsaiStorageError::Trie("Couldn't fetch node in db")
.According to @AurelienFT this could be due to the db trying to access the key to replace it while it hasn't yet been committed to storage.
Expected behavior:
Bonsai db should be able to handle double insertions without having to
commit
to storage.Steps to reproduce:
Perform double insertion of the same key into a bonsai db in a single commit.
Related code:
The function currently crashing:
preload_node_subtree
The text was updated successfully, but these errors were encountered: