Implement history node deletion logic #1443
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
wxing1292
force-pushed
the
events-chaining-delete-node
branch
4 times, most recently
from
e1509f0
to
d60c9fa
Compare
* SQL: Rename SelectFromHistoryNode to RangeSelectFromHistoryNode * SQL: Rename DeleteFromHistoryNode to RangeDeleteFromHistoryNode * SQL: New DeleteFromHistoryNode aiming to delete one record from history node table
wxing1292
force-pushed
the
events-chaining-delete-node
branch
from
d60c9fa
to
808041e
Compare
alexshtin
approved these changes
Apr 13, 2021
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.
What changed?
Why?
Pre-requisite of events chaining
How did you test it?
Existing test & new tests
Potential risks
N/A
Is hotfix candidate?
No