Michael Bayer (@zzzeek) wrote:

Remove deprecation warnings mysql5 7 20

MySQL 5.7.20 now warns for use of the @tx_isolation variable; a version
check is now performed and uses @transaction_isolation instead
to prevent this warning.

For 1.1, also backport our_warn() test fixture fix from
9f0fb6c 1.2 branch.

(cherry picked from commit 41cfe44)
Co-authored by: Mike Bayer mike_mp@zzzcomputing.com
Fixes: #4120
Pull-request: zzzeek/sqlalchemy#391
Change-Id: I4d2e04df760c5351a71dde8b32145cdc69fa6115

→ 71c9b49

Changes by Michael Bayer (@zzzeek):

• changed status to closed

Michael Bayer (@zzzeek) wrote:

Remove deprecation warnings mysql5 7 20

MySQL 5.7.20 now warns for use of the @tx_isolation variable; a version
check is now performed and uses @transaction_isolation instead
to prevent this warning.

Co-authored by: Mike Bayer mike_mp@zzzcomputing.com
Fixes: #4120
Change-Id: I4d2e04df760c5351a71dde8b32145cdc69fa6115
Pull-request: zzzeek/sqlalchemy#391

→ 41cfe44

Kim Myhrman wrote:

Hi :)
Why is it backported to 1.1.15 and not 1.1.14, then it is impossible to fix the issue since 1.1.15 is not released?

Michael Bayer (@zzzeek) wrote:

I'll tell you how releases work. The number "1.1.14" is carved in stone - it is up on pypi at https://pypi.python.org/pypi/SQLAlchemy/1.1.14 and I cannot change anything about the 1.1.14 file. 1.1.15 is the next release in the 1.1 series which contains the fix, and you'll be able to upgrade to it directly, as soon as I release, which was hopefully this week. We mark bugs as "fixed" when they are committed for their target release, not when the actual release is put out. You can certainly download a tar.gz of 1.1.15 from here or github just by using the 1.1 branch (e.g. https://github.com/zzzeek/sqlalchemy/archive/rel_1_1.zip).