| Bug #66465 | MySQLCursorRaw, fetchall() raises exception if there are unread results | ||
|---|---|---|---|
| Submitted: | 20 Aug 2012 14:54 | Modified: | 12 Sep 2012 3:54 |
| Reporter: | an p | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / Python | Severity: | S3 (Non-critical) |
| Version: | 1.0.5 | OS: | Any |
| Assigned to: | Geert Vanderkelen | CPU Architecture: | Any |
[20 Aug 2012 14:56]
an p
How to repeat: # self.c is a RAW cursor of a connection
[21 Aug 2012 5:51]
Geert Vanderkelen
Thanks for reporting this problem. There is indeed a 'not' missing in the Python v3 code.
[12 Sep 2012 3:55]
Geert Vanderkelen
Fix in MySQL Connector/Python v1.0.6 beta.

Description: When calling fetchall() on a raw cursor an InterfaceError is CALLED IF THERE ARE UNREAD RESULTS How to repeat: # self.c is a cursor of a connection self.c.execute(reqString, parameters) rows = self.c.fetchall() Suggested fix: in the method fetchall() of MySQLCursorRaw, file: cursor.py, line: 794 794 if self._have_unread_result(): 795 InterfaceError("No result set to fetch from.") I think there is a "not" missing like in MySQLCursor's version of fetchall()