Skip to content

Add option to use Standard SQL dialect in BigQuery #13615

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.

Sign up for GitHub

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

Jump to bottom
Closed
RoyalTS opened this issue Jul 11, 2016 · 1 comment
Closed

Add option to use Standard SQL dialect in BigQuery #13615

RoyalTS opened this issue Jul 11, 2016 · 1 comment
Milestone
0.19.0

Comments

@RoyalTS
Copy link

RoyalTS commented Jul 11, 2016

BigQuery now sports a SQL dialect that's compatible with the 2011 SQL standard. Queries are still run using BigQuery's Legacy SQL dialect at the moment (see https://cloud.google.com/bigquery/sql-reference/enabling-standard-sql) but they may soon switch to Standard SQL by default. pandas.io.gbq.read_gbq() should therefore have an argument that determines the SQL dialect that's used to run the query.
@jorisvandenbossche
Copy link
Member

cc @parthea @aaront @jacobschaer

@parthea parthea mentioned this issue Jul 30, 2016
Closed
parthea added a commit to parthea/pandas that referenced this issue Aug 2, 2016
@parthea
Allow users to specify whether gbq should use standard SQL pandas-dev…
e1fbb07 
…#13615
@jreback jreback added this to the 0.19.0 milestone Aug 3, 2016
@jreback jreback closed this as completed in 97de42a Aug 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.19.0
Development

Successfully merging a pull request may close this issue.

Allow users to specify whether gbq should use standard SQL parthea/pandas
3 participants
@RoyalTS @jreback @jorisvandenbossche