-
Notifications
You must be signed in to change notification settings - Fork 138
fix: unnest failed in some cases (with table references failed when there were no other references to refrenced tables in a query) #290
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
Conversation
Reviewer: This PR is explained pretty well, I think, by the comment here: Mostly unrelated, I added the missing |
And expand comment
} | ||
|
||
# By convention, dialect-provided types are spelled with all upper case. | ||
STRING = _type_map["STRING"] | ||
BOOL = _type_map["BOOL"] | ||
ARRAY = _type_map["ARRAY"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does the new array type count as a feature? Perhaps it'd look better in the changelog as a separate PR?
If it is a feature and it doesn't make sense to split out, we could also try the multi-change commit message feature when we squash and merge this: https://github.com/googleapis/release-please#what-if-my-pr-contains-multiple-fixes-or-features
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not a new feature. It was just missing from the types list.
SQLAlchemy has basic array support that works with BigQuery (thanks to some previous effort on our part).
@@ -34,6 +34,7 @@ | |||
import datetime | |||
import decimal | |||
|
|||
sqlalchemy_version_info = tuple(map(int, sqlalchemy.__version__.split("."))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works, though I've been trying to use https://packaging.pypa.io/en/latest/version.html which is the canonical version parser. We already have it pulled in via a transitive dependency through setuptools
, I believe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. I'll switch to that.
WRT how we get it, IMO, anything we import should be a direct dependency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. I'm fine explicitly including it in our dependencies / test dependencies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Co-authored-by: Tim Swast <swast@google.com>
…-sqlalchemy into fix-unnest-283
@tswast are you cool with this? :) |
I have to more small PRs coming that will build on this. |
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #283 🦕