Skip to content
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

Fix!: use maybe_parse in exp.to_table so they have parity #1684

Merged
merged 6 commits into from
May 24, 2023

Conversation

georgesittas
Copy link
Collaborator

No description provided.

sqlglot/expressions.py Outdated Show resolved Hide resolved
sqlglot/expressions.py Outdated Show resolved Hide resolved
@georgesittas georgesittas changed the title Fix: allow >3 table parts in exp.to_table Fix!: allow >3 table parts in exp.to_table May 24, 2023
@georgesittas georgesittas changed the title Fix!: allow >3 table parts in exp.to_table Fix!: use maybe_parse in exp.to_table to get parity between them May 24, 2023
@georgesittas georgesittas changed the title Fix!: use maybe_parse in exp.to_table to get parity between them Fix!: use maybe_parse in exp.to_table so they have parity May 24, 2023
@georgesittas georgesittas merged commit e995ab0 into main May 24, 2023
@georgesittas georgesittas deleted the jo/to_table_fixup branch May 24, 2023 22:00
adrianisk pushed a commit to adrianisk/sqlglot that referenced this pull request Jun 21, 2023
tobymao#1684)

* Fix: allow >3 table parts in exp.to_table

* Fix mypy types

* Keep parity between to_table and _parse_table by using maybe_parse

* Refactor bigquery _parse_table_parts

* Fix exp.Table expression parser

* Fixup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants