Repository navigation
Conversation
Cover the same February day in a common year and a leap year, then step backwards from leap day into January. These cases distinguish carrying a source month-end from clamping to a shorter target month. Assisted-by: OpenAI Codex:GPT-6 Percentage of AI-generated code: 100% Signed-off-by: Dyu-young <2245387130@qq.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Thanks for contributing to IvorySQL! |
Closes #3338.
Add three cases to the Oracle-mode datetime regression suite. Moving February 28 forward one month reaches March 31 in a common year and March 28 in a leap year. Moving February 29 backward one month reaches January 31. The SQL and expected output are the only files changed.
Verification
475ab195with the patch applied and ranmake -j1 -C contrib/ivorysql_ora oracle-check TAP_TESTS=. All 36 SQL regression tests passed.OpenAI Codex (GPT-6) generated the test changes. The human contributor's DCO sign-off and AI attribution are recorded in the commit.
Summary by CodeRabbit
ADD_MONTHSaround February month-end dates in leap and non-leap years, including moving forward and backward by one month.