v26.24.3 release notes: clarify TIMESTAMP fix scope#36643
Merged
Conversation
…estamps 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 <noreply@anthropic.com>
maheshwarip
approved these changes
May 20, 2026
Contributor
|
@martykulma would love your eyes on this before we merge |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #36641. The original v26.24.3 bug-fix entry read as though #36612 also handled zero-value timestamps (
0000-00-00 00:00:00). It does not — those still requireTEXT COLUMNSplus an explicitCASTin user queries. This PR adjusts the wording to make that clear.