hey eskil, thanks for the bugreport.
On 02/06/2010 Eskil Olsen wrote: > Package: python-mysqldb > Version: 1.2.2-10 > > 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. the bugreport contains a different patch than you attached to your mail. > Patch has also been submitted to python-mysqldb at sourceforge. unfortunately i cannot find either of the patches (the one from upstream mysql-python sourceforge bug tracking system, and the one you attached to this debian bugreport) applied against upstream mysql-python sources. neither in svn, nor in hg repository. please point me to the upstream source where one of the patches has been applied. greetings, jonas
signature.asc
Description: Digital signature
_______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
