From f62c2f22c6b040c6341ca6baf89985de3715f43a Mon Sep 17 00:00:00 2001 From: Jon Currey Date: Wed, 20 May 2026 15:16:59 -0400 Subject: [PATCH] v26.24.3 release notes: clarify TIMESTAMP fix scope vs zero-value timestamps The TIMESTAMP/DATETIME decode fix in #36612 covers ordinary values ingested via TEXT COLUMNS, but the special zero-value timestamps still require TEXT COLUMNS plus an explicit CAST in user queries. Update the v26.24.3 bug fix entry to avoid implying the zero-value case is also fully handled. Co-Authored-By: Claude --- doc/user/content/releases/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/user/content/releases/_index.md b/doc/user/content/releases/_index.md index 95ffe3def8165..6743fd464951a 100644 --- a/doc/user/content/releases/_index.md +++ b/doc/user/content/releases/_index.md @@ -23,8 +23,8 @@ This patch release fixes a MySQL source ingestion bug. ### Bug Fixes {#v26.24.3-bug-fixes} - Fixed MySQL sources failing to decode `TIMESTAMP` and `DATETIME` columns - ingested via `TEXT COLUMNS`, including MySQL's special zero-value timestamps - (`0000-00-00 00:00:00`). + ingested via `TEXT COLUMNS`. Zero-value timestamps (`0000-00-00 00:00:00`) + continue to require `TEXT COLUMNS` plus a `CAST` in user queries. ## v26.24.2 *Released to Materialize Self-Managed: 2026-05-18*