-
Notifications
You must be signed in to change notification settings - Fork 176
Render query modifications #80
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
Render query modifications #80
Conversation
1. Add basic 'HAVING' clause (before the 'ORDER BY' clause). 2. Select source tables in 'DATE_RANGE' format. 3. Add 'BETWEEN' clause in conditions. 4. Modify 'ORDER BY' to accept multiple parameters.
Test cases modified as the ORDER_BY syntax has changed and HAVING clause also has been added.
Update Table and Patch Table support has been added.
Render the conditions for the having clause. Moved the 'GROUP BY' clause defination abouve 'HAVING'.
Check the length of the value is 2, when BETWEEN is used. If length is not equal to 2 throw warning.
else: | ||
return {} | ||
|
||
def patch_table(self, dataset, table, schema, expiration_time=None): |
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.
patch_table
already exists: https://github.com/tylertreat/BigQuery-Python/blob/master/bigquery/client.py#L487
It looks like the client.py changes don't belong with the query_builder.py changes. |
Removed the client.py changes from the query_builder.py On Wed, Feb 3, 2016 at 5:00 AM, Tyler Treat notifications@github.com
|
Deleted the un-correct code for patch_table and update_table.
Updated the query builder API.