fix(drive): update grovedb after just in time fix #1426
Merged
Conversation
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
shumkov
changed the title
…y/platform into fix/updateGroveDBForJustInTimeFix
…y/platform into fix/updateGroveDBForJustInTimeFix
strophy
previously approved these changes
Sep 28, 2023
strophy
approved these changes
Sep 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue being fixed or feature implemented
There was an issue before with just in time updates that would lead to corrupted states.
What was done?
In GroveDb, just in time updates are now done at insertion/update time and not at commit time.
How Has This Been Tested?
Ran all platform tests, and re-enabled previously breaking tests.
Breaking Changes
There was a breaking change in grovedb
Checklist:
For repository code-owners and collaborators only