Refactor so storage detects if Insert fails because of unique constraint#6259
Merged
Conversation
Contributor
|
Surge PR preview deployment was removed |
This comment was marked as off-topic.
This comment was marked as off-topic.
qwerty287
reviewed
Mar 19, 2026
qwerty287
approved these changes
Mar 19, 2026
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
3 participants
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.
a followup of #6228 that focus on make server storage aware if failed inserts because of unique constraint by introducing new error type
also we rename the old
RecordNotExisttoErrRecordNotExistto satisfy the error lint requirements that our linter currently is missing somehow