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

Send TIMESTAMP query parameters as strings. #2891

Merged
merged 1 commit into from
Dec 20, 2016
Merged

Send TIMESTAMP query parameters as strings. #2891

merged 1 commit into from
Dec 20, 2016

Conversation

tseaver
Copy link
Contributor

@tseaver tseaver commented Dec 20, 2016

  • Not the float-time-since-epoch-in-seconds which Bigquery uses for all other TIMESTAMP values. :(
  • Not RFC3339, but the SQL-mandated format with an embedded space. :(

Closes: #2886.

/cc @tswast

- *Not* the float-time-since-epoch-in-seconds which Bigquery uses for
  all other TIMESTAMP values. :(
- *Not* RFC3339, but the SQL-mandated format with an embedded space. :(

Closes: #2886.
@tseaver tseaver added api: bigquery Issues related to the BigQuery API. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Dec 20, 2016
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Dec 20, 2016
@@ -150,7 +150,11 @@ def _bytes_to_json(value):
def _timestamp_to_json(value):

This comment was marked as spam.

This comment was marked as spam.

@tseaver tseaver merged commit a8fb997 into googleapis:master Dec 20, 2016
@tseaver tseaver deleted the 2886-bigquery-timestamp-query-parm branch December 20, 2016 20:03
richkadel pushed a commit to richkadel/google-cloud-python that referenced this pull request May 6, 2017
…mp-query-parm

Send TIMESTAMP query parameters as strings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the BigQuery API. cla: yes This human has signed the Contributor License Agreement. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants