[11.x] Apply relation constraints on upsert #52239
Merged
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.
Currently when using
upsert
via a relationship (HasOne
,HasMany
,MorphOne
,MorhpMany
) we need to pass the foreign key (and morph type) explicitly.For example I have a
User
model with a has many relation calledconsents
. Before this PR we have to pass theuser_id => 4
explicitly for the records (for polymorphic relation the morph type as well).After the PR these values are filled automatically:
In other relationship methods like
create
,updateOrCreate
orsave
Eloquent already does the job for us.