Expose Cursor.warning_count#1056
Merged
Merged
Conversation
After the removal of automatic warnings in PyMySQL#774 this provides a way to check for existence of warnings without having to perform an additional query over the network.
Nothing4You
force-pushed
the
warning-count
branch
from
958eec6 to
d6b9e30
Compare
|
This is exactly what I needed :) |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In #774 automatic warnings were removed.
As far as I can tell there is currently no public API to access
cursor._result.warning_count.This provides a way to check for existence of warnings without having to perform an additional query over the network.