-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
SQLAlchemy Version 2.0.0 breaks reflected tables #43
Comments
I faced the same issue with my team, until we go through the migration docs, I created a Fork for this repo (https://github.com/2904nando/sqlalchemy-aurora-data-api-1-4-46) which blocks the SQLAchemy version on setup.py to < 2. This is just a workaround, but it gives us time to review the 2.0 migration docs before going forward. |
This was the same workaround our team did, though we just set an explicit dependency of "sqlalchemy<2" in requirements.txt of our app. |
To fix this specific error, I guess you should add a text on any String direct SQL command sent on your code. Example: From:
To:
This applies to any direct SQL statement sent by the DB connection.
from the migration docs (https://docs.sqlalchemy.org/en/14/changelog/migration_20.html) |
I am having an issue since SQLAlchemy was updated yesterday as part of dependency discovery, since then it appears to install version 2.0.0 of the main library
vs what it was doing a day ago
After this we have been forced to update from the old table reflection method to the new
OLD
NEW (from what i could gather from the docs:
However its causing this big long error:
Any ideas as to why it fails now? Are we performing the table reflections incorrectly or is there some kind of library issue with the new version?
Docs:
https://docs.sqlalchemy.org/en/20/core/reflection.html#reflecting-all-tables-at-once
https://docs.sqlalchemy.org/en/14/changelog/migration_20.html
The text was updated successfully, but these errors were encountered: