Reverted "Fixed #26140 -- Suppressed MySQL warning when inserting binary content"#7324
Closed
timgraham wants to merge 1 commit into
Closed
Reverted "Fixed #26140 -- Suppressed MySQL warning when inserting binary content"#7324timgraham wants to merge 1 commit into
timgraham wants to merge 1 commit into
Conversation
…ary content" This reverts commit 204e00c as mysqlclient 1.3.8 is now handling the issue.
Member
Author
|
Hm, still doesn't entirely work. Will look more tomorrow. |
Member
|
In the short term, I would fix the mysqlclient version to 1.3.7 in the test requirements. We'll then see how the mysqlclient maintainer reacts about the regressions (there are two differents). |
Member
Author
|
Closing as mysqlclient 1.3.9 has reverted the problematic change. |
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.
This reverts commit 204e00c as mysqlclient
1.3.8 is now handling the issue.