Who is throwing (and catching) this MySQL Exception?

Question

i'm using Python with MySQL and Django. I keep seeing this error and I can't figure out where the exception is being thrown:

Exception _mysql_exceptions.ProgrammingError: (2014, "Commands out of sync; you can't run this command now") in <bound method Cursor.__del__ of <MySQLdb.cursors.Cursor object at 0x20108150>> ignored

I have many "try" and "exception" blocks in my code--if the exception occurred within one of those, then I would see my own debugging messages. The above Exception is obviously being caught somewhere since my program does not abort when the Exception is thrown.

I'm very puzzled, can someone help me out?

Answer 1

I had exactly that error (using MySQLdb and Django) and discovered that the reason it was "ignored" was that it occurred in a __del__ method. Exceptions in __del__ are categorically ignored: object.__del__ datamodel

There doesn't seem to be any way to catch it from further up the stack (at least according to this thread), but you can edit MySQLdb/cursors.py or monkey-patch to get your own __del__ in there that catches the exception and drops you into a pdb prompt or logs a full traceback.

Answer 2

This is a Python Error.

See: http://eric.lubow.org/2009/python/pythons-mysqldb-2014-error-commands-out-of-sync/

It looks like there is a problem with your MySQLdb Query.