Is that `Date` variable type is parsed to DATE instead of TIMESTAMP in 50.36

There isn't any error with Metabase 0.49.25.2 when I add 'Asia/Saigon' to the DATE() function, but when I upgrade to 0.50.36, it meets this error with Date variables

Variable name: start_date
Variable type: Date

SELECT ...
FROM ...
WHERE DATE({{start_date}}, 'Asia/Saigon')

Error:

400 Bad Request POST https://bigquery.googleapis.com/bigquery/v2/projects/aha-move-staging-348509/queries { "code": 400, "errors": [ { "domain": "global", "location": "q", "locationType": "parameter", "message": "No matching signature for function DATE\n Argument types: DATE, STRING\n Signature: DATE(TIMESTAMP, [STRING])\n Argument 1: Unable to coerce type DATE to expected type TIMESTAMP\n Signature: DATE(DATETIME)\n Signature accepts at most 1 argument, found 2 arguments\n Signature: DATE(INT64, INT64, INT64)\n Signature requires at least 3 arguments, found 2 arguments\n Signature: DATE(DATE)\n Signature accepts at most 1 argument, found 2 arguments\n Signature: DATE(STRING)\n Signature accepts at most 1 argument, found 2 arguments at [12:68]", "reason": "invalidQuery" } ], "message": "No matching signature for function DATE\n Argument types: DATE, STRING\n Signature: DATE(TIMESTAMP, [STRING])\n Argument 1: Unable to coerce type DATE to expected type TIMESTAMP\n Signature: DATE(DATETIME)\n Signature accepts at most 1 argument, found 2 arguments\n Signature: DATE(INT64, INT64, INT64)\n Signature requires at least 3 arguments, found 2 arguments\n Signature: DATE(DATE)\n Signature accepts at most 1 argument, found 2 arguments\n Signature: DATE(STRING)\n Signature accepts at most 1 argument, found 2 arguments at [12:68]", "status": "INVALID_ARGUMENT" }

Hi @Luiggi, could you help me ?

Hi there,

Testing around (on v55), I'm seeing that:
SELECT DATE({{start_date}}, 'Asia/Saigon')
becomes
SELECT DATE(date "2025-06-24", 'Asia/Saigon')
Which fails because this call to DATE requires the first parameter to be a timestamp.

But something like this could work:
SELECT DATE(timestamp ({{start_date}}), 'Asia/Saigon')

Which converts to:
SELECT DATE(timestamp (date "2025-06-24"), 'Asia/Saigon')

Yes, we also fix it by adding timestamp() function, but this critical change of Metabase causes all cards which using this function fall into error, why don't they have a highlight of this change ?