On Wed, Jun 02, 2010 at 11:14:02AM -0700, Eskil Olsen wrote: > There is a missing check in _mysql.c _mysql_ResultObject_Initialize, where a > failed SELECT that ends in a deadlock, returns a NULL from mysql_store > result, but according to > http://dev.mysql.com/doc/refman/5.0/en/null-mysql-store-result.html, you > have to check errno or num_fields afterwards. > > Not doing this, causes exceptions to be silently dropped. > > Here's a similar bugreport > http://sourceforge.net/tracker/?func=detail&aid=2776267&group_id=22307&atid=374932 > > Attached is a patch that fixes the problem in _mysql.c. It was made against > 1.2.3, but applies to 1.2.2 with some fuzz. > > Patch has also been submitted to python-mysqldb at sourceforge.
Is this still the case with the lastest python-mysqldb in unstable? -- Brian May <b...@debian.org>
