feat: delete dirty data when insert fails#3681
Merged
dl239 merged 5 commits into4paradigm:mainfrom Jan 16, 2024
Merged
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3681 +/- ##
============================================
- Coverage 78.27% 74.90% -3.38%
- Complexity 0 654 +654
============================================
Files 553 729 +176
Lines 120481 131138 +10657
Branches 0 1341 +1341
============================================
+ Hits 94312 98233 +3921
- Misses 26153 32606 +6453
- Partials 16 299 +283 ☔ View full report in Codecov by Sentry. |
lqy222
approved these changes
Jan 15, 2024
vagetablechicken
approved these changes
Jan 16, 2024
This file contains hidden or 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
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 kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?