-
Notifications
You must be signed in to change notification settings - Fork 79
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 dialect has_table
doesn't use the schema name.
#115
Comments
unj1m
changed the title
SQLAlchemy dialect
SQLAlchemy dialect May 2, 2023
has_table
doesn't ise the schema name.has_table
doesn't use the schema name.
Agree. Having the same experience. This is a simple fix. I've changed it locally (allowed for schema name to get passed to DESCRIBE TABLE) and it works without issue. |
@susodapop Can we get someone assigned to this ticket? |
susodapop
added a commit
that referenced
this issue
Jul 11, 2023
Closes #115 Signed-off-by: Jesse Whitehouse <jesse.whitehouse@databricks.com>
This was referenced Jul 11, 2023
susodapop
added a commit
that referenced
this issue
Jul 11, 2023
Closes #115 Signed-off-by: Jesse Whitehouse <jesse.whitehouse@databricks.com>
susodapop
added a commit
that referenced
this issue
Jul 12, 2023
Closes #115 Signed-off-by: Jesse Whitehouse <jesse.whitehouse@databricks.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
has_table gets the schema namebut doesn't pass it to
DESCRIBE
.This causes SQLAlchemy to fail to drop a given table (in a given schema).
The text was updated successfully, but these errors were encountered: