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

Official fork of PyMySQL supporting Tornado #2

Open
YuzhongHuangCS opened this issue Feb 20, 2015 · 6 comments
Open

Official fork of PyMySQL supporting Tornado #2

YuzhongHuangCS opened this issue Feb 20, 2015 · 6 comments

Comments

@YuzhongHuangCS
Copy link

I just find that PyMySQL have an official fork that support Tornado.
https://github.com/PyMySQL/Tornado-MySQL

I suggest merge this repo back or abandon.

@mosquito
Copy link
Contributor

I tested tormysql vs tornado-mysql. Tormysql was fastest 1.5-2 times.

https://gist.github.com/mosquito/aa20b94fec8b406d9a51

@zen-young-chan
Copy link

Error, This can't connet to the mysql, i have use password !

OperationalError: (2003, 'Can't connect to MySQL server on localhost:3306 (InternalError(1698, u"Access denied for user 'root'@'localhost'"))')

@ctgaff
Copy link

ctgaff commented Oct 10, 2017

Great job on this module. I also find it much faster then Tornado-MySQL and it handles reusing sockets via the connection pool very efficiently. This is a much better implementation.

@snower
Copy link
Owner

snower commented Jan 4, 2018

Tormysql now runs asyncio on its own, does not depend on tornado, and is faster and more efficient than the official aiomysql.

@ploxiln
Copy link
Contributor

ploxiln commented Feb 6, 2018

It seems the developer of PyMySQL/Tornado-MySQL is no longer interested in developing it, since about 1.75 years ago. It seems appropriate to close this issue.

@AivanF
Copy link

AivanF commented Nov 23, 2018

It seems the developer of PyMySQL/Tornado-MySQL is no longer interested in developing it, since about 1.75 years ago. It seems appropriate to close this issue.

Indeed! It doesn't support MySQL 8 and never will – the author told me that. The issue is not an issue anymore :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants