Bug #67649 | DB session unusable if unbuffered cursor is closed before fetching all results | ||
---|---|---|---|
Submitted: | 20 Nov 2012 11:42 | Modified: | 10 Jul 2013 13:18 |
Reporter: | Rudy Metzger | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / Python | Severity: | S3 (Non-critical) |
Version: | 1.0.7 | OS: | Linux (Fedora 17) |
Assigned to: | Geert Vanderkelen | CPU Architecture: | Any |
[20 Nov 2012 11:42]
Rudy Metzger
[26 Nov 2012 9:40]
Geert Vanderkelen
Unfortunately, they only ways out is either to read the complete the result, or close/open the connection (reconnect). You can't tell MySQL to just forget about the result and simply continue.
[26 Nov 2012 9:42]
Geert Vanderkelen
But, I agree, the error message could be better, or should.
[10 Jul 2013 13:18]
Paul DuBois
Noted in 1.0.12, 1.1.1 changelogs. An unclear OperationalError was raised if a cursor object was closed while there were unread results. Connector/Python now raises an InternalError indicating that there are still unread results. This provides information that to avoid the error it is necessary to consume the result by reading all rows.