[NFC/Unit test] - Failing test demonstrating blank timestamp updates #20891
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.
Overview
This will fail at the moment.
In civicrm/civicrm-packages#319 insert() was patched to also look for timestamp db fields when inserting a blank date in a field that allows nulls. But update() was not also patched so it has the same problem with timestamp types.
Before
DB Error: unknown error
Incorrect datetime value: '0' for column
whatever
at row 1After
After civicrm/civicrm-packages#326, stores null in the db
Technical Details
It only fails if sql_mode has NO_ZERO_DATE.
Comments
#20476