[int] Catch ValueError when formatting SQL statement logs#8642
Open
sfayer wants to merge 1 commit into
Open
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
1 participant
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,
This is my simpler fix to avoid needing mogrify in the mysql library: If there is an unescaped formatting character in the SQL statement, the logging will throw ValueError. By catching it here, it'll raise a proper ProgrammingError from the mysql library instead, which will hopefully make it clearer that something is wrong.
Regards,
Simon
BEGINRELEASENOTES
*Core
FIX: Catch ValueError when formatting SQL statement logs
ENDRELEASENOTES