MySQLdb gets wedged once any query returns an info
message with warnings. Subsequent queries throw the
exception belonging to the query that produced the info
This patch fixes the bug but I think it might be better
if Cursor.messages were changed from an array to a
string and renamed Cursor.message. I don't understand
why you'd want more messsages around than the one from
the latest query--it seems like a memory leak.
For MySQLdb/cursors.py from MySQL-python-0.9.2c1.
Log in to post a comment.