-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix datetime field with empty default #166
Merged
JanJakes
merged 9 commits into
WordPress:develop
from
wojtekn:fix/datetime-field-with-empty-default
Dec 19, 2024
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3c5455a
v2.1.14 (#155)
aristath a2661f9
Merge branch 'develop'
aristath e43782e
Add test that reproduces issue with invalid empty date default
wojtekn 056bb18
Remove trailing space
wojtekn 674bb6f
Add more cases to the test
wojtekn 7835a5e
Ensure that for empty default date fields there is no default
wojtekn 7f43961
Fix lint issues
wojtekn e81a812
Fix one more lint issue
wojtekn 86b43fd
Fxi support for valid date field default values
wojtekn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wojtekn This seems to remove all defaults for date/time fields, including valid defaults, such as
col YEAR DEFAULT '2024'
. Could we add a test case with a valid default for each of these data types, and ensure that it is preserved?My guess is that the problem could be that the original condition, despite looking fine (
'' !== $column->dflt_value
), might be missing the fact that the default can include a quoted string, so it should be rather something like'' !== trim( $column->dflt_value, "'" )
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking further, what's tricky, though, is that the
''
value as a default is valid for string fields. So I guess we need to trim the quotes only for the case of non-string or date/time fields?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I untangled the conditions to handle all cases and make it more readable in 86b43fd