fix(cast format): Correct behavior of YEAR pattern#9052
Open
TreeHunter9 wants to merge 3 commits into
Open
Conversation
added 3 commits
June 5, 2026 14:36
…erns Only names was incorrect, usage of these variables was correct;
This pattern was taken from Oracle and should represent `spelled out year (TWENTY TWENTY SIX)`. In it current implementation it was similar to YYYY (just year as number (2026)), which is incorrect.
…plemented YEAR pattern
TreeHunter9
changed the title
YEAR pattern
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
1 participant
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.
spelled out year (TWENTY TWENTY-SIX). In the current implementation, it was equivalent toYYYY(i.e., the year as a number (2026)), which is incorrect;YEARpattern;TO_STRING_PATTERNSandTO_DATETIME_PATTERNS(usage was correct);