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 <himurakenshi...@gmail.com>
wrote:
> Thanks for the reply, Mike.
>
> Actually there is no obvious errors, furthermore with a l
>
>
> 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
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:*
