-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return correct response if unique index violation happened on SQLite backend #3353
Merged
rumyantseva
merged 4 commits into
FerretDB:main
from
rumyantseva:issue-3183-fix-indexes
Sep 14, 2023
Merged
Return correct response if unique index violation happened on SQLite backend #3353
rumyantseva
merged 4 commits into
FerretDB:main
from
rumyantseva:issue-3183-fix-indexes
Sep 14, 2023
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
Codecov Report
@@ Coverage Diff @@
## main #3353 +/- ##
==========================================
+ Coverage 74.03% 74.11% +0.07%
==========================================
Files 413 413
Lines 25292 25305 +13
==========================================
+ Hits 18726 18755 +29
+ Misses 5475 5465 -10
+ Partials 1091 1085 -6
Flags with carried forward coverage won't be shown. Click here to find out more. |
rumyantseva
changed the title
Fix indexes for SQLite
Return the correct response in case unique index violation happened on SQLite backend
Sep 13, 2023
rumyantseva
changed the title
Return the correct response in case unique index violation happened on SQLite backend
Return the correct response if unique index violation happened on SQLite backend
Sep 13, 2023
rumyantseva
changed the title
Return the correct response if unique index violation happened on SQLite backend
Return correct response if unique index violation happened on SQLite backend
Sep 13, 2023
noisersup
approved these changes
Sep 13, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
chilagrow
approved these changes
Sep 14, 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.
Description
Closes #3183.
The approach with
WriteError
is the same as inmsg_insert
for consistency purposes.Readiness checklist
task all
, and it passed.@FerretDB/core
), Milestone (Next
), Labels, Project and project's Sprint fields.