Re: [sqlalchemy] Re: Python 3.5 mysql-connector==2.1.6 SQLAlchemy==1.1.11 queue Empty

2017-07-17 Thread josip povreslo
Mike, Just as an info, mysql-connector is a total NO for us, when I switched to mysql-connector we saw bigger problems and those happens much more often. PyMySQL is the last thing to switch to and try. For this processing piece I'm thinking to replace SQLAlchemy with a direct database driver

Re: [sqlalchemy] Re: Python 3.5 mysql-connector==2.1.6 SQLAlchemy==1.1.11 queue Empty

2017-07-17 Thread Mike Bayer
On Mon, Jul 17, 2017 at 4:23 AM, josip povreslo wrote: > To add more information to it: > > We are running our dB on AWS RDS, this is what MySQL say in logs when we > switched to mysql-connector: Oh. That is an *extremely* different situation.Amazon RDS is a MySQL

Re: [sqlalchemy] Re: Python 3.5 mysql-connector==2.1.6 SQLAlchemy==1.1.11 queue Empty

2017-07-17 Thread josip povreslo
To add more information to it: We are running our dB on AWS RDS, this is what MySQL say in logs when we switched to mysql-connector: [Note] Aborted connection 9191 to db: 'connstr' (Got an error reading communication packets) Best Regards, Josip On Monday, July 17, 2017 at 9:47:50 AM UTC+2,

Re: [sqlalchemy] Re: Python 3.5 mysql-connector==2.1.6 SQLAlchemy==1.1.11 queue Empty

2017-07-17 Thread josip povreslo
Yep, that's where I've stopped with my research for now. Mysqlclient handles relatively ok for now although I think as well it's a problem with network there, wouldn't be the first time. Eithter way, thanks for your support, I'll get back with full details if/when I completely understand

Re: [sqlalchemy] The right way to use gevent with sqlalchemy

2017-07-17 Thread Tony Wang
Hi Mike Great thanks, error seems gone. On Sun, Jul 16, 2017 at 11:37 PM Mike Bayer wrote: > it means like this (here, I adapt your SqlHelper into a recipe that is > basically equivalent to the context manager at > >

[sqlalchemy] Bug report with JSON nulls in 1.1.x

2017-07-17 Thread vineet
Hello, I'd like to report a bug report regarding JSON nulls and underscore-prefixed attributes as we're upgrading from 1.0.17 to 1.1.11. I read through the behavior at http://docs.sqlalchemy.org/en/latest/changelog/migration_11.html#change-3514 and