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

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] Re: Python 3.5 mysql-connector==2.1.6 SQLAlchemy==1.1.11 queue Empty

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

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

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

Thanks! On Saturday, July 15, 2017 at 12:08:19 AM UTC+2, Mike Bayer wrote: > > I've set up > https://bitbucket.org/zzzeek/sqlalchemy/issues/4028/move-cant-connect-handling-outside-of > > to deal with the misleading "pool.Empty" error for 1.2, though that is > not the problem you're having

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

Thanks Mike! Point valid, it's mysqlclient==1.3.9, we don't have MySQL-Python installed, inherited the system so I assumed it's mysql-connector from some reason, nevertheless. Hmmm, I was afraid that's the actual case (connection error). We were checking the connection limits and that's not

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

I've set up https://bitbucket.org/zzzeek/sqlalchemy/issues/4028/move-cant-connect-handling-outside-of to deal with the misleading "pool.Empty" error for 1.2, though that is not the problem you're having here. On Fri, Jul 14, 2017 at 5:57 PM, Mike Bayer wrote: > that

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

that "mysqldb" URL is not mysql-connector - it's MySQL-Python (old and unmaintained) or mysqlclient (much better, if you have it installed and not conflicting w/ MySQL-Python). You'd need to specify "mysql+mysqlconnector://" to use that DBAPI, but also I'd recommend trying "mysql+pymysql://" to

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

In addition to the previous email, what I do is the following: When request comes in: self.mysql_engine = create_engine('mysql+mysqldb://{}:{}@{}/{}'.format(self.db_params['dbuser'], self.db_params['dbpass'], self.db_params['db_hosts'][db_host_index], self.db_params['dbname']),