-
Notifications
You must be signed in to change notification settings - Fork 2
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
Dialect: Fix get_table_names()
reflection method
#10
Conversation
56bd4b6
to
1070b37
Compare
01218be
to
2f08b2a
Compare
1070b37
to
5ddc8e1
Compare
2f08b2a
to
43c45fb
Compare
get_table_names()
reflection methodget_table_names()
reflection method
7198467
to
62a6bb4
Compare
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
This item is reviewed and the missing things done, we can merge it @amotl |
Excellent. Thank you very much. Please note it is a stacked PR, so others need to be merged first, or the branch needs to be set up differently. Otherwise, it will cause a mess at GH-9. |
0f85790
to
20443d2
Compare
632ca49
to
8d8e732
Compare
This comment was marked as resolved.
This comment was marked as resolved.
9557d1c
to
36d8b3d
Compare
…gument It did not respect the `schema` query argument in SQLAlchemy connection URLs. Co-authored-by: Marios Trivyzas <[email protected]>
9020756
to
6ac0a22
Compare
We don't know which circumstances cause this problem. SQLAlchemy 1.3 is EOL anyway, so we don't care too much. sqlalchemy.exc.InvalidRequestError: When initializing mapper mapped class RootStore->root, expression 'ItemStore' failed to locate a name ('ItemStore').
About
The
get_table_names()
reflection method did not respect theschema
query argument in SQLAlchemy connection URLs.This improvement has been used successfully on a few downstream projects and is known as the inspector patch. This patch brings it to mainline.
References
Backlog