Metabase ClickHouse date filters ignore report timezone: session_timezone not sent

If Metabase date filters on ClickHouse return rows that straddle the month boundary, first check the version: this was fixed and backported to the 58.x through 64.x lines, so upgrading is the real fix. To confirm you are hitting this bug and not a data issue, run a native question with SELECT timezone(), getSetting('session_timezone'); if it does not return your report timezone, the session timezone is not being applied and relative filters will misbehave. Workaround on affected versions: use explicit date ranges instead of relative filters, or wrap the column with toTimeZone in a custom column so the grouping uses the right zone.

Context: GitHub issue metabase/metabase#79671 (closed, 7 comments): with a ClickHouse database and the Metabase report timezone set to anything other than UTC, relative date filters like Current month silently selected the wrong rows: timestamps from the end of the previous month leaked in and rows from the end of the current month were dropped. The ClickHouse driver claimed to set sessiontimezone but the setting never reached the server, verified by running SELECT timezone(), getSetting('sessiontimezone') as a native question, which returned UTC and an empty value.