SQLAlchemy dialect has_table doesn't use the schema name. #115

Activity

1. unj1m

   changed the title [-]SQLAlchemy dialect `has_table` doesn't ise the schema name.[/-] [+]SQLAlchemy dialect `has_table` doesn't use the schema name.[/+] on May 2, 2023
2. narquette commented on Jul 10, 2023

   

   narquette

   on Jul 10, 2023

   Last edited by narquette

   More actions

   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.
3. narquette commented on Jul 10, 2023

   

   narquette

   on Jul 10, 2023

   More actions

   @susodapop Can we get someone assigned to this ticket?
4. susodapop

   self-assigned this

   on Jul 11, 2023
5. susodapop

   added 3 commits that reference this issue on Jul 11, 2023

   Update has_table to honor schema selection and allow for catalog select

   ...

   This issue will close once commit 530e2bd is merged into the 'main' branch.

   530e2bd

   Update has_table to honor schema selection and allow for catalog select

   ...

   This issue will close once commit 2388873 is merged into the 'main' branch.

   2388873

   Update has_table to honor schema selection and allow for catalog select

   ...

   This issue will close once commit 159355d is merged into the 'main' branch.

   159355d
6. susodapop

   closed this as completedin #174on Jul 12, 2023
7. eric-wang-1990

   added 2 commits that reference this issue on Jul 16, 2026

   chore(bots): bump engine to 3963f4b (post-#115); use REPO_ROOT not TE…

   ...

   0d31c76

   feat(bots): local install-bot-engine + bot-prelude composites (PAT-free)

   ...

   30e34bc
8. nikolasd

   added a commit that references this issue on Sep 8, 2026

   feat(bots): onboard reviewer-bot to pinned databricks-bot-engine (dat…

   ...

   3e29a62