Expose Cursor.warning_count#780
Draft
Copilot wants to merge 2 commits into
Draft
Conversation
Copilot
AI
changed the title
[WIP] Add cursor.warning_count to mysqlclient
Expose Jun 8, 2026
Cursor.warning_count
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
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 ports PyMySQL’s
Cursor.warning_countbehavior to mysqlclient so callers can inspect whether the last operation produced warnings without issuing an extra round-trip. It also keeps unbuffered cursors in sync once the result stream is fully consumed.What changed
Cursor.warning_countto the base cursor state.Connection.warning_count()after each query result is obtained.Unbuffered cursor behavior
SSCursor.warning_countwhen the result set is exhausted via:fetchone()fetchmany()fetchall()Regression coverage
DROP TABLE IF EXISTSon a missing table)0on a warning-free statement