mysql-compatibility: update ZERO_DATE docs (#5154) #5233
Merged
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.
cherry-pick #5154 to release-5.0
What is changed, added or deleted? (Required)
The behavior of zero_date changed in master to be more mysql compatibility. This has not been backported.
There are some minor exceptions still, since DDL changes can still produce invalid dates (see: pingcap/tidb#21564 ). But I think these are minor, and it is worth updating the docs since the main workflow as described (INSERT/UPDATE) now matches MySQL.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?