clamp dates with invalid years to 0 #38
Closed
Conversation
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
Asp er the MySQL documentation DATE and DATETIME only support ranges from '1000-01-01 00:00:00' to '9999-12-31 23:59:59', and TIMESTAMP from '1970-01-01 00:00:01.000000' to '2038-01-19 03:14:07.999999'. Values outside those ranges are not guaranteed to work. Additionally it mentions that invalid values are converted to their appropriate zero value. The patch converts dates that lead to an exception right now to their zero value. This is more lenient than what the ranges given in the documentation. The behaviour set through zeroDateTimeBehavior applies to these zero values. This fixes Bug#94872.
|
Hi, thank you for your contribution. Please confirm this code is submitted under the terms of the OCA (Oracle's Contribution Agreement) you have previously signed by cutting and pasting the following text as a comment: |
|
I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it. |
|
Hi, thank you for your contribution. Your code has been assigned to an internal queue. Please follow |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Asp er the MySQL documentation DATE and DATETIME only support ranges from
'1000-01-01 00:00:00' to '9999-12-31 23:59:59', and TIMESTAMP from
'1970-01-01 00:00:01.000000' to '2038-01-19 03:14:07.999999'. Values outside
those ranges are not guaranteed to work. Additionally it mentions that invalid
values are converted to their appropriate zero value.
The patch converts dates that lead to an exception right now to their zero
value. This is more lenient than what the ranges given in the documentation.
The behaviour set through zeroDateTimeBehavior applies to these zero values.
This fixes Bug#94872.