Re: [sqlalchemy] NoSuchColumnError happens when multiple processes concurrently access to a row with locking

2016-04-19 Thread Mike Bayer
step one is to make the behavior go away, then you can bisect versions of mysql-python (assuming that was the problem) to figure out the specific issue. Very little has happened with mysql-python between 1.2.3 and 1.2.5 so if that's where the problem is it wouldn't be very hard to figure out.

Re: [sqlalchemy] NoSuchColumnError happens when multiple processes concurrently access to a row with locking

2016-04-19 Thread Shingo Toda
Thank you very much for your quick response. I will try your suggestion. I just wonder if you know there is any bug fix e.g. identical commit log for this as, if possible, I want a kind of evidence that upgrading the driver could solve my problem. On Tuesday, April 19, 2016 at 10:56:06 PM

Re: [sqlalchemy] NoSuchColumnError happens when multiple processes concurrently access to a row with locking

2016-04-19 Thread Mike Bayer
On 04/18/2016 08:54 PM, Shingo Toda wrote: Hi all I am now seeing the SQLAlchemy raise 'NoSuchColumnError' occasionally when concurrent accesses happen with 'select for update'. My application uses * SQLAlchemy 0.8.4 * MySQL-python 1.2.3 * CentOS6.7 * python 2.6 *

[sqlalchemy] NoSuchColumnError happens when multiple processes concurrently access to a row with locking

2016-04-18 Thread Shingo Toda
Hi all I am now seeing the SQLAlchemy raise 'NoSuchColumnError' occasionally when concurrent accesses happen with 'select for update'. My application uses * SQLAlchemy 0.8.4 * MySQL-python 1.2.3 * CentOS6.7 * python 2.6 * MariaDB 10.0.20 (three-node Galera Cluster with