Why Eager loading (with) in Laravel? - Purpose & Use Cases

The Big Idea

Discover how a simple change can make your app lightning fast and save hours of debugging!

The Scenario

Imagine you have a blog with posts and each post has many comments. You want to show a list of posts with their comments. So, you write code that fetches each post, then for each post, you fetch its comments separately.

The Problem

This means if you have 10 posts, you run 1 query to get posts and then 10 more queries to get comments for each post. This is slow and wastes resources. It also makes your app feel laggy and can crash if there are many posts.

The Solution

Eager loading lets you tell Laravel to get posts and their comments in just 2 queries: one for posts and one for all related comments. This is faster, cleaner, and uses less memory.

Before vs After

✗ Before

$posts = Post::all();
foreach ($posts as $post) {
  $comments = $post->comments;
}

✓ After

$posts = Post::with('comments')->get();

What It Enables

Eager loading makes your app faster and smoother by reducing database queries automatically.

Real Life Example

When showing a product list with reviews on an online store, eager loading fetches all products and their reviews efficiently, so customers see everything instantly.

Key Takeaways

Manual fetching causes many slow database queries.

Eager loading fetches related data in fewer queries.

This improves app speed and user experience.

Practice

1. What is the main purpose of using with() in Laravel Eloquent queries?

easy

A. To delete related models automatically

B. To load related models in the same query to reduce database calls

C. To paginate the results of a query

D. To sort the results by a related model's attribute

Solution

1. Step 1: Understand what with() does

   The with() method tells Laravel to load related models eagerly, meaning it fetches them in the same database query or fewer queries.

2. Step 2: Identify the benefit of eager loading

   This reduces the number of database queries, improving performance by avoiding the N+1 query problem.

3. Final Answer:

   To load related models in the same query to reduce database calls -> Option B

4. Quick Check:

   Eager loading = fewer queries = better performance [OK]

Hint: Remember: with() loads related data upfront [OK]

Common Mistakes:

• Thinking with() deletes related data
• Confusing with() with pagination
• Assuming with() sorts results

2. Which of the following is the correct syntax to eager load the 'comments' relationship on a Post model?

easy

A. Post::with('comments')->get();

B. Post::fetch('comments')->all();

C. Post::eager('comments')->all();

D. Post::load('comments')->get();

Solution

1. Step 1: Recall the correct method for eager loading

   Laravel uses the with() method to eager load relationships before fetching results.

2. Step 2: Check the syntax correctness

   Post::with('comments')->get(); correctly calls with() and then get() to retrieve posts with comments.

3. Final Answer:

   Post::with('comments')->get(); -> Option A

4. Quick Check:

   with() + get() = eager load [OK]

Hint: Use with() before get() to eager load [OK]

Common Mistakes:

• Using load() statically instead of on model instance
• Using non-existent methods like eager() or fetch()
• Calling get() before with()

3. Given the code:

 $users = User::with('posts')->get();
foreach ($users as $user) {
  echo $user->posts->count();
}

What will this code output?

medium

A. An error because posts is not loaded

B. The total number of users instead of posts

C. Always zero because posts are not counted

D. The number of posts for each user without extra queries

Solution

1. Step 1: Understand eager loading effect

   The with('posts') loads all posts for each user in one query, so $user->posts is available without extra queries.

2. Step 2: Analyze the loop output

   For each user, $user->posts->count() returns the number of posts related to that user, printed one by one.

3. Final Answer:

   The number of posts for each user without extra queries -> Option D

4. Quick Check:

   with() loads posts, count() shows posts per user [OK]

Hint: with() loads related data, so count() works without errors [OK]

Common Mistakes:

• Assuming posts are not loaded and cause errors
• Thinking count() returns total users
• Confusing eager loading with lazy loading

4. Identify the error in this code snippet:

$orders = Order::with('customer')->get();
foreach ($orders as $order) {
  echo $order->customer->name;
}

Assuming the 'customer' relation is defined correctly, what is the likely problem?

medium

A. Using with() after get() instead of before

B. Missing parentheses on customer relation call

C. Accessing customer without checking if it exists

D. Using get() instead of first()

Solution

1. Step 1: Check eager loading usage

   The with('customer') is correctly used before get(), so related customers are loaded.

2. Step 2: Identify potential null relation access

   Some orders might not have a customer, so $order->customer could be null, causing an error when accessing name without a check.

3. Final Answer:

   Accessing customer without checking if it exists -> Option C

4. Quick Check:

   Null relation access causes error, check before use [OK]

Hint: Always check if related model exists before accessing properties [OK]

Common Mistakes:

• Thinking with() must come after get()
• Assuming relation always exists
• Confusing get() and first() usage

5. You want to eager load the 'comments' and their 'author' for each post efficiently. Which code correctly achieves this?

hard

A. Post::with(['comments.author'])->get();

B. Post::load('comments.author')->get();

C. Post::with(['comments', 'author'])->get();

D. Post::with('comments', 'author')->get();

Solution

1. Step 1: Understand nested eager loading syntax

   To eager load a relation of a relation, use dot notation inside an array: with(['comments.author']).

2. Step 2: Analyze each option

   Post::with('comments', 'author')->get(); loads comments and author separately, but author is not a direct relation of Post. Post::load('comments.author')->get(); uses load() statically, which is invalid as load() is an instance method. Post::with(['comments', 'author'])->get(); loads comments and author separately as array elements, but author is not direct relation. Post::with(['comments.author'])->get(); correctly loads comments and their author nested.

3. Final Answer:

   Post::with(['comments.author'])->get(); -> Option A

4. Quick Check:

   Nested relations use dot notation inside array [OK]

Hint: Use dot notation inside array for nested eager loading [OK]

Common Mistakes:

• Passing multiple relations as separate strings without array
• Using load() statically
• Trying to load unrelated models directly