Fix history ids #873
Merged
Fix history ids #873
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
abitmore
approved these changes
Apr 24, 2018
|
Question: since the bug is affecting 3rd-party businesses especially exchanges that integrated/listed BTS and/or other BitShares assets, should we tag a hotfix release for this? |
abitmore
requested changes
Apr 24, 2018
abitmore
approved these changes
Apr 25, 2018
16 tasks
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.
Fixes #585
The first time we need to skip an operation_history ID we use create/remove, this will store the previous "next_id" in undo_database. For subsequent operations we still use use_next_id for better performance.