When using DATE parameter in BigQuery connection, Metabase automatically adds timezone as REPORT TIMEZONE (we chose Asia/Saigon), so with BigQuery DATE default function convert it to UTC and it is not correct date for end users.
current_date: 08 May 2023 18:00:00
DATE filter: 08-05-2023
BigQuery query: select {{date}}, DATE({{date}}), DATE({{date}}, 'Asia/Saigon')
=> the result:
May 8, 2023, 00:00
May 7, 2023
May 8, 2023

Note: metabase version v0.46.1

What’s the data type of the field in the database?

I ask about timezone issue of DATE parameter with BigQuery connection. Of course I use date type to compare with the parameter

It shows incorrect about DATE({{date}}) value, It should be 'May 1, 2023'

why don't you switch the report timezone to "database default"?

I know BigQuery database works if we config report timezone is "database default", but it does not work with other database like Postgres (it will be GMT although default timezone is 'Asia/Saigon').

Addtional, I wan to ask and report because this may be bug: the same config, the same DATE parameter but Metabase has 2 output value with 2 different versions