Has anyone run into this?
Warehouse: ClickHouse 25.6, plain MergeTree
dbt adapter: dbt-clickhouse 1.9
unique_key: vat_number
strategy: check
check_cols: [registration_number] # only one stable column
dbt_valid_to_current: toDateTime(‘2100-01-01 00:00:00’)
query_settings:
join_use_nulls: 1
apply_mutations_on_fly: 1 # also tried mutations_sync=1Behavior:
First snapshot run – writes one row, dbt_valid_to = 2100-01-01 00:00:00 
Second run after a real data change – old row is closed (dbt_valid_to = now()), but the new “current” row is also saved with dbt_valid_to = now() instead of 2100-01-01 
Third run (no data change) – third row emerges with correct dbt_valid_to value - dbt_valid_to = 2100-01-01 00:00:00 .
Why would the INSERT … VALUES (…) sometimes use current time instead of the configured future date?