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

default to useLegacySql = NULL, instead of useLegacySql = TRUE #134

Closed
fhoffa opened this issue Nov 22, 2016 · 1 comment
Closed

default to useLegacySql = NULL, instead of useLegacySql = TRUE #134

fhoffa opened this issue Nov 22, 2016 · 1 comment

Comments

@fhoffa
Copy link

fhoffa commented Nov 22, 2016

9c539c7

#standardSQL as a header will make your queries work as standard, without specifying it

but if it is specified, then the query fails

For example, the tool Exploratory.io that relies on bigrquery started failing my queries when bigrquery got this path.

Can we have useLegacySql default to NULL for most library users, except for those that want to explicitly use standard?

Test:

#standardSQL
select COUNT(*)
from fh-bigquery.public_dump.numbers_255

(this should work when useLegacySql=NULL, and fail if the #standardSQL header is removed)

@hadley
Copy link
Member

hadley commented Apr 18, 2017

Now part of #147

@hadley hadley closed this as completed Apr 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants