We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
fh-bigquery.public_dump.numbers_255
(this should work when useLegacySql=NULL, and fail if the #standardSQL header is removed)
The text was updated successfully, but these errors were encountered:
Now part of #147
Sorry, something went wrong.
No branches or pull requests
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)
The text was updated successfully, but these errors were encountered: