Skip to content

[5.7] "Constraining Eager Loads" callout for unsupported eager load limit() #4918

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 20, 2019
Merged

[5.7] "Constraining Eager Loads" callout for unsupported eager load limit() #4918

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion eloquent-relationships.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -927,7 +927,7 @@ You may not always need every column from the relationships you are retrieving.
<a name="constraining-eager-loads"></a>
### Constraining Eager Loads

Sometimes you may wish to eager load a relationship, but also specify additional query constraints for the eager loading query. Here's an example:
Sometimes you may wish to eager load a relationship, but also specify additional query conditions for the eager loading query. Here's an example:

$users = App\User::with(['posts' => function ($query) {
$query->where('title', 'like', '%first%');
Expand All @@ -939,6 +939,8 @@ In this example, Eloquent will only eager load posts where the post's `title` co
$query->orderBy('created_at', 'desc');
}])->get();

> {note} Query builder methods `limit()` and `take()` cannot be used when constraining eager loads. One database query is run to eager load a relation so the limited results will be for _all_ models, not _per_ model.

<a name="lazy-eager-loading"></a>
### Lazy Eager Loading

Expand Down