#8 Only one warning

MySQLdb
closed
MySQLdb (53)
5
2012-09-19
2002-06-23
Rob Steele
No

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
message.

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.

MySQLdb rocks!

Discussion

  • Rob Steele

    Rob Steele - 2002-06-23
     
    Attachments
  • Andy Dustman

    Andy Dustman - 2002-06-23

    Logged In: YES
    user_id=71372

    You're might be right that it's broken, but a bigger problem
    is that it's not correctly implementing what's in PEP-249.
    I'll rework this for c2. Thanks for the heads-up.

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks