Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pymysql error 1193 Unknown system variable tx_isolation #5161

Closed
ifuchs opened this issue Feb 19, 2020 · 8 comments
Closed

pymysql error 1193 Unknown system variable tx_isolation #5161

ifuchs opened this issue Feb 19, 2020 · 8 comments
Labels
mysql question issue where a "fix" on the SQLAlchemy side is unlikely, hence more of a usage question

Comments

@ifuchs
Copy link

ifuchs commented Feb 19, 2020

I just upgraded MySQL to the current version 8 (from a very old version) and now I find that I am getting an error on engine.connect of the form (pymysql.err.internalError) (1193, Unknown system variable' tx_isolation). I am running sqlalchemy v 13.13 and pymysql v 0.9.3.

@zzzeek zzzeek added mysql question issue where a "fix" on the SQLAlchemy side is unlikely, hence more of a usage question labels Feb 19, 2020
@zzzeek
Copy link
Member

zzzeek commented Feb 19, 2020

hi there -

something about your MySQL server is not sending out a version detection string that is expected. Can you go to your MySQL console and send the results of:

"SELECT VERSION()"

example:

Server version: 8.0.16 MySQL Community Server - GPL

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MySQL [(none)]> SELECT VERSION();
+-----------+
| VERSION() |
+-----------+
| 8.0.16    |
+-----------+
1 row in set (0.006 sec)

@zzzeek
Copy link
Member

zzzeek commented Feb 19, 2020

also please indicate if you are using any kind of high level proxy servers like ProxySQL or MaxScale.

@ifuchs
Copy link
Author

ifuchs commented Feb 19, 2020 via email

@ifuchs
Copy link
Author

ifuchs commented Feb 19, 2020 via email

@zzzeek
Copy link
Member

zzzeek commented Feb 19, 2020

yes I have a feeling you were running an old SQLAlchemy somehwere. do you have a stack trace from the error scenario?

@zzzeek
Copy link
Member

zzzeek commented Mar 3, 2020

no issue here

@Skyler1017
Copy link

same issue here...
I am using mysql 5.6.28

@Skyler1017
Copy link

upgrade sqlalchemy and the problem is solved!
1.1.0 -> 1.3.18

hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mysql question issue where a "fix" on the SQLAlchemy side is unlikely, hence more of a usage question
Projects
None yet
Development

No branches or pull requests

3 participants