fix(core): allow users to specify createdAt
in updateOnDuplicate
#17379
+1
−1
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.
Fixes issue #17347
Pull Request Checklist
Description of Changes
Allows to provide
createdAt
field inupdateOnDuplicate
option to enable updating thecreatedAt
timestamp on duplicate. In older versions (<2018) it was possible to provide a boolean to enable all fields to be updated on duplicate, however this behavior is not supported anymore and users need to explicitly provide a list of field names allowing finer grained control over what's updated. The explicit exclusion ofcreatedAt
is thus no longer necessary and simply a remainder of the old, removed functionality.List of Breaking Changes