Re: [sqlalchemy] Re: SQLAlchemy 1.2.0b1 released

Great! Thank you!. Good to know the behavior hasn't changed. We have a lot of "read-only" routes or database-free routes which rely on the "lazy" transaction/connection behavior for performance. I was worried the new flag could create db connectivity per-request when the session is

Re: [sqlalchemy] Re: SQLAlchemy 1.2.0b1 released

the Session doesn't pull the connection from the engine until you do a query or call session.connection(), session.execute(), etc. This is because the Session supports multiple engines simultaenously and it doesn't know which one to use until it's asked to query something. On Tue, Jul 11, 2017 at

Re: [sqlalchemy] Re: SQLAlchemy 1.2.0b1 released

On Tuesday, July 11, 2017 at 10:27:15 AM UTC-4, Mike Bayer wrote: > > So the note for this is at: > > > http://docs.sqlalchemy.org/en/latest/changelog/migration_12.html#pessimistic-disconnection-detection-added-to-the-connection-pool > > > then in the main docs, the new flag replaces the

Re: [sqlalchemy] Debugging complex SQLAlchemy applications

On Tue, Jul 11, 2017 at 7:34 AM, Pavel S wrote: > Hi, > > I maintain extremely complex application (>100k LOC) which uses SQLAlchemy. > Often in the log I find errors like: > > sqlalchemy/engine/default.py:450: Warning: Truncated incorrect DOUBLE value: > 'Foo' > > or > >

Re: [sqlalchemy] Re: SQLAlchemy 1.2.0b1 released

On Mon, Jul 10, 2017 at 5:58 PM, Jonathan Vanasco wrote: > > > On Monday, July 10, 2017 at 9:44:03 AM UTC-4, Mike Bayer wrote: >> >> * Connection pool pre-ping - The connection pool now includes an >> optional "pre ping" feature that will test the "liveness" of a pooled >>

[sqlalchemy] Debugging complex SQLAlchemy applications

Hi, I maintain extremely complex application (>100k LOC) which uses SQLAlchemy. Often in the log I find errors like: sqlalchemy/engine/default.py:450: Warning: Truncated incorrect DOUBLE value: 'Foo' or sqlalchemy/sql/sqltypes.py:201: SAWarning: Unicode type received non-unicode bind param