fix: fix isUniqueConstraintError to catch SQL Server error 2627#60320
Merged
Conversation
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
2 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.
Hi @taylorotwell,
SqlServerConnection::isUniqueConstraintErroronly caught error 2601 but missed error 2627 because the regex required "row" in the message. Error 2601 says "Cannot insert duplicate key row in object" while 2627 says "Cannot insert duplicate key in object" (no "row"). This caused UNIQUE KEY and PRIMARY KEY constraint violations to throw a genericQueryExceptioninstead ofUniqueConstraintViolationException. Fixed by making "row" optional.https://learn.microsoft.com/en-us/sql/relational-databases/errors-events/database-engine-events-and-errors-2000-to-2999