-
Notifications
You must be signed in to change notification settings - Fork 132
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
feat: Handle passing of arrays to in statements more efficiently in SQLAlchemy 1.4 and higher #253
Merged
Merged
Changes from all commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
8dcb7a3
Add last_query fixture to make it easier to look at recent queries
jimfulton 17f0507
Don't expand in lists for SQLAlchemy 1.4
jimfulton 5908802
Merge branch 'master' into no-expand
jimfulton ff21918
blacken/lint
jimfulton 39dfdf9
Merge branch 'master' into no-expand
jimfulton 86e75a9
merge upstream/master
jimfulton 0eb6a12
Merge branch 'master' into no-expand
jimfulton 018e398
Merge branch 'master' into no-expand
jimfulton 9343b86
Simplify visit_bindparam and punt on literal binds, to work less hard…
jimfulton 5104979
Merge remote-tracking branch 'upstream' into no-expand
jimfulton c2c0bf4
blacken
jimfulton 04c5751
Restored some code needed by compliance tests
jimfulton 23b4b73
Merge branch 'no-expand' of github.com:jimfulton/python-bigquery-sqla…
jimfulton bc615e6
blacken
jimfulton 83227a6
Merge branch 'master' into no-expand
jimfulton 7fc5d55
Merge branch 'master' into no-expand
jimfulton 3fe81d3
Merge branch 'master' into no-expand
jimfulton 56e943e
merge upstream/master
jimfulton 295b1bc
Add a comment explainin the expanding logic.
jimfulton 6e32630
removed dup test
jimfulton ba3b476
merge upstream/master
jimfulton c51389c
Merge branch 'master' into no-expand
jimfulton bbfcd57
merge upstream/master
jimfulton 6a9596f
Merge branch 'no-expand' of github.com:jimfulton/python-bigquery-sqla…
jimfulton File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Should the type of
param_2
beARRAY<INT64>
?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.
No, because the BQ DB API does special handling of arrays.
It sees that we have a scalar type of INT64 and that we have a sequence, and then creates a
ArrayQueryParameter
.It happens that since I added struct support, passing
ARRAY<INT64>
would probably work (because I have to handle structs of arrays). But just usngINT64
works too.