[8.x] Clarify required timestamp columns for pivot tables #6427
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.
After researching laravel/framework#34548 I've come to the conclusion that pivot tables always require both a
created_at
andupdated_at
column because of their behavior of inheriting parent timestamp column names. This isn't immediately clear because for regular Eloquent models you can disable them by settingstatic::CREATED_AT
and/orstatic::UPDATED_AT
tonull
. So it's best to clarify the specific behavior here.It could also be that we just don't support setting these constants to
null
in the first place and that both acreated_at
andupdated_at
column are always required? If so, then I think we should explicitly state that somewhere in the docs.