Skip to content
This repository was archived by the owner on May 16, 2026. It is now read-only.

fix: avoid creating aliases for already-known tables - #361

Merged
tswast merged 1 commit into
mainfrom
353-no-alias-for-known-table
Oct 26, 2021
Merged

fix: avoid creating aliases for already-known tables#361
tswast merged 1 commit into
mainfrom
353-no-alias-for-known-table

Conversation

@tseaver

Copy link
Copy Markdown
Contributor

Closes#353.

@tseaver
tseaver requested review from a team and tswastOctober 26, 2021 18:41
@google-clagoogle-claBot added the cla: yes This human has signed the Contributor License Agreement. label Oct 26, 2021
@product-auto-labelproduct-auto-labelBot added the api: bigquery Issues related to the googleapis/python-bigquery-sqlalchemy API. label Oct 26, 2021

@tswasttswast left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

api: bigqueryIssues related to the googleapis/python-bigquery-sqlalchemy API.cla: yesThis human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unnest function in BigQuery SQLAlchemy plugin joins twice when selecting other columns

2 participants

@tseaver@tswast