Re: [sqlalchemy] Problem with 'fetchone'

Add some updates here. I found every time I got this problem, the affected rows is 18446744073709552000. On Tue, Jul 19, 2016 at 2:13 AM, Tian JiaLin wrote: > Thanks for the reply, Mike. > > Actually there is no obvious errors, furthermore with a lower percentage >

Re: [sqlalchemy] Problem with 'fetchone'

Thanks for the reply, Mike. Actually there is no obvious errors, furthermore with a lower percentage occurrences. That's why I feel this is pretty hard to debug. And I did the similar thing like the snippets you provided to invalidate the broken connections. I'm not using any session variables

Re: [sqlalchemy] Problem with 'fetchone'

On 07/18/2016 12:15 PM, Tian JiaLin wrote: Hi Everyone, I have been using MySQL-Python for a long time. Recently I tried to integrated a connection pool which is based on SQLAlchemy, In terms of the legacy code, I'm using the raw_connection from the engine. Here is the sample code of two

[sqlalchemy] Problem with 'fetchone'

Hi Everyone, I have been using MySQL-Python for a long time. Recently I tried to integrated a connection pool which is based on SQLAlchemy, In terms of the legacy code, I'm using the raw_connection from the engine. Here is the sample code of two implementations: *No Pool Version:*