Respect --allow-zero-in-date in CREATE and in -declarative migrations #9142
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.
Followup to #9089
This PR respects
--allow-zero-in-date
forddl_strategy
in the following:CREATE TABLE
statement, whether online or not-declarative
migration, whether it turns out to be an actualCREATE TABLE
or anALTER TABLE
.I believe this completes and covers all cases for
--allow-zero-in-date
.endtoend
tests added for validation.Documentation PR to follow.
Checklist
Deployment Notes