Support BigQuery database driver

[mbobrovskyi]

Add support for BigQuery database driver.

[StevenACoffman]

Hey, I was comparing against #830 and I was just curious if you were going to pick this back up.

[mbobrovskyi]

Hey, I was comparing against #830 and I was just curious if you were going to pick this back up.

Hi. I haven't found a stable emulator for the bigquery. That's why there are a lot of mistakes in testing.

BTW, it is working with real data.

[StevenACoffman]

Oh, have you tried https://github.com/goccy/bigquery-emulator ? I used it for a handful of tests and it worked reasonably well there. The DDL support is mostly CREATE TABLE | VIEW | FUNCTION, and corresponding DROP TABLE | VIEW | FUNCTION https://github.com/goccy/go-zetasqlite#status so it doesn't have all the ALTER support that one might want.

[mbobrovskyi]

Oh, have you tried https://github.com/goccy/bigquery-emulator ? I used it for a handful of tests and it worked reasonably well there. The DDL support is mostly CREATE TABLE | VIEW | FUNCTION, and corresponding DROP TABLE | VIEW | FUNCTION https://github.com/goccy/go-zetasqlite#status so it doesn't have all the ALTER support that one might want.

Unfortunately bigquery-emulator didn't allow to use system variables. We are using it to set automaticaly '@@dataset_id' in migrations scripts. I have create issue for this case (goccy/bigquery-emulator#147).

And alse the problem is that dktest does not allow to open a custom port. I created a pull request (dhui/dktest#21) in order to allow opening the port manually, but so far no one has approved it.

[mbobrovskyi]

/cc @dhui

[mbobrovskyi]

I'm not sure what's happening with the tests. It seems to be an issue with sqlserver. However, these changes are unrelated to that. I also tried to run it on master and I have the same issue.

[mbobrovskyi]

Created an issue #1174.