Bigquery can only handle legacy SQL

[GaryLiuTelus]

Bigquery now is mainly non-legacy SQL, so it should include --use_legacy_sql=false parameter (https://cloud.google.com/bigquery/docs/bq-command-line-tool).
my current url is bigquery:?project_id=xxx&dataset_id=xxxx&use_legacy_sql=false
currently, dadbod wrap the final command as
bq --project_id=xxx --dataset_id=xxxx --use_legacy_sql=false query 'actual SELECT clause',

vim-dadbod/autoload/db/adapter/bigquery.vim

Line 25 in e95afed

return cmd + [a:subcmd]

but this will throw an error: FATAL Command 'use_legacy_sql=false' unknown.

According to the official document above, the bq command should be with query together and then other parameters, like

bq query --project_id=xxx --use_legacy_sql=false 'actual SELECT'

Please see below comparisons

<<=============Edit=================>>
https://cloud.google.com/bigquery/docs/bq-command-line-tool#positioning_flags_and_arguments

For bq command, there are global flags and command-specific flags.
--use_legacy_sql=false is command-specific flag (for query command) so it should be put after query command.

[s-hammon]

As per the docs, probably just makes the most sense to put this in ~/.bigqueryrc:

[query]
--use_legacy_sql=false

That said, I'm not sure why legacy SQL is the default for bq when nearly everything else (many client libraries, even GCP's own web-based console) uses the standard/Google SQL or whatever it's called.

For reference, something like this might be useful:

{
	"tpope/vim-dadbod",
	config = function()
		local home = vim.fn.expand("$HOME")
		local rc_path = home .. "/.bigqueryrc"

		local f = io.open(rc_path, "r")
		if f then
			f:close()
			return
		end

		local out = io.open(rc_path, "w")
		if out then
			out:write("[query]\n--use_legacy_sql=false\n")
			out:close()
			vim.notify("Created ~/.bigqueryrc (--use_legacy_sql=false)", vim.log.levels.INFO)
		else
			vim.notify("Failed to write ~/.bigqueryrc", vim.log.levels.ERROR)
		end
	end,
}