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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken RowProxy
import with sqlalchemy 1.4
#298
Comments
RowProxy
import with sqlalchemy 1.4
- as per encode/databases#298, sqlalchemy 1.4 removed `RowProxy` which causes `databases` to fail
- as per encode/databases#298, sqlalchemy 1.4 removed `RowProxy` which causes `databases` to fail
- as per encode/databases#298, sqlalchemy 1.4 removed `RowProxy` which causes `databases` to fail
- as per encode/databases#298, sqlalchemy 1.4 removed `RowProxy` which causes `databases` to fail
- as per encode/databases#298, sqlalchemy 1.4 removed `RowProxy` which causes `databases` to fail
Oh, so SQLAlchemy 1.4 is out now? That's great! PR fixing deps welcome <3 |
I'm not very familiar with |
I have the same problem here, I am using pymysql.
|
Hi! One more issue for 1.4 sqlalchemy/sqlalchemy#6096 |
@rajasimon please pin dependencies to version if you are having problems. |
Using |
I'd suggest that the sensible first pass for us would be to issue a new release of We can then follow up with a PR that adds support for both 1.3 and 1.4, but we'll be under less time pressure to do so, so we're more likely to get it right, and users will have a working |
@tomchristie Please do the needful update to have a support for 1.4 SQLAlchemy version |
The
RowProxy
importdatabases/databases/backends/sqlite.py
Line 8 in 932c5d1
RowProxy
in 1.4 馃槙The text was updated successfully, but these errors were encountered: