Check UTC rendering separately from ClickHouse view timestamp identity
Check the text contract of a UTC view separately from epoch preservation. Recording the actual session timezone with output text tests the consumer requirement without mistaking a display difference for a shifted instant.
Type names cannot approve both contracts
Instant preservation and displayed timezone are separate contracts. A view’s type name cannot approve both. Truthound Core can compare prepared output text with an independently declared UTC rendering while epoch identity is checked separately. [1, 2, 3]
Right epoch and different text
ClickHouse issue #129459 reports 26.8.34.13-lts on macOS returning a typed DateTime(UTC) view in the session timezone while toTypeName says UTC. The epoch is reported unchanged, and the latest release was not run. Follow-up comments describe investigation. [1]
Record the session context
Record epoch, toTypeName, rendered text, and session_timezone for each view row. Compare the text with the UTC contract rather than concluding that the underlying instant moved. Include the explicit CAST-inside-view control. [1, 3]
One UTC rendering for an instant
For epoch 1767225600, expected UTC text=2026-01-01 00:00:00. That passes. Text 2026-01-01 05:30:00 fails a UTC display contract even though it can represent the same instant in Asia/Kolkata. The comparison is about rendering, not an invented epoch change. [1, 3]
Prepare formatting deliberately
ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares operator-prepared non-null text columns with ==. The operator defines formatting and records actual session context. The SDK does not apply a ClickHouse view conversion or certify the instant from dtype metadata. [1, 2, 3]
Check explicit CAST and epoch
Verify the reported explicit CAST in the view SELECT and approve text and epoch conditions separately. Do not assume a declared typed column list performs the same conversion in every server version. [1, 3]
The export consumer needs the distinction
A consumer exporting UTC text needs this check even if an internal epoch join remains correct. Conversely, a display mismatch alone is insufficient evidence of corrupted event order. [1, 3]
Application conditions
Prepare epoch, declared type, session zone, and rendered UTC text together.
Alternatives
Verify explicit CAST inside the view, checking epoch and text separately.
Limitations
Do not infer an instant shift or damaged history from rendering alone.
Evidence
- Event checked
- Subject checked
- Modified
