One-to-many (hasMany) in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does the hasMany relationship represent in Laravel?

It represents a one-to-many relationship where one model owns many related models. For example, a blog post can have many comments.

beginner

How do you define a hasMany relationship in a Laravel model?

Inside the model, create a method that returns $this->hasMany(RelatedModel::class). This tells Laravel the model owns many related models.

beginner

In a one-to-many relationship, which table contains the foreign key?

The table of the related model (the "many" side) contains the foreign key that points back to the "one" side model.

intermediate

What is the output when you access a hasMany relationship property in Laravel?

You get a collection of related models. For example, $post->comments returns a collection of all comments for that post.

intermediate

Why is it important to use hasMany instead of manually querying related models?

Using hasMany keeps your code clean, readable, and leverages Laravel's built-in features like eager loading and query optimization.

Which method defines a one-to-many relationship in a Laravel model?

A hasOne()

B belongsTo()

C hasMany()

D belongsToMany()

The hasMany() method defines a one-to-many relationship where one model owns many related models.

Where is the foreign key stored in a one-to-many relationship?

A In the "many" side model's table

B In the "one" side model's table

C In a pivot table

D No foreign key is needed

The foreign key is stored in the "many" side model's table pointing back to the "one" side.

What type of data does accessing a hasMany relationship return?

A A collection of models

B A single model instance

C A boolean value

D An integer count

Accessing a hasMany relationship returns a collection of related model instances.

Which of these is a benefit of using Laravel's hasMany relationship?

A Manual SQL queries only

B Automatic eager loading and cleaner code

C No need for foreign keys

D Only works with one record

Laravel's hasMany provides automatic eager loading and keeps code clean and readable.

How do you access related models in a hasMany relationship?

A $model->relatedModel()

B $model->relatedModel->first()

C $model->relatedModel->count()

D $model->relatedModel

You access related models as a property, e.g., $model->relatedModel, which returns a collection.

Explain how to set up a one-to-many (hasMany) relationship in Laravel and how it works.

Think about how one thing can have many related things in your app.

Describe the benefits of using Laravel's hasMany relationship instead of manual database queries.

Consider how Laravel helps you write less code and avoid mistakes.

Practice

1. What does the hasMany relationship represent in Laravel?

easy

A. One model has many related models

B. Many models belong to one model

C. One model belongs to one other model

D. Many models have many related models

Solution

1. Step 1: Understand relationship types

   Laravel defines relationships to connect models. hasMany means one model owns many related models.

2. Step 2: Match relationship to description

   hasMany is used when one record relates to multiple records in another table.

3. Final Answer:

   One model has many related models -> Option A

4. Quick Check:

   hasMany = one-to-many [OK]

Hint: hasMany means one owns many others [OK]

Common Mistakes:

• Confusing hasMany with belongsTo
• Thinking hasMany means many-to-many
• Mixing up owner and owned models

2. Which of the following is the correct way to define a hasMany relationship in a Laravel model?

easy

A. public function comments() { return $this->belongsTo(Comment::class); }

B. public function comments() { return $this->hasMany(Comment::class); }

C. public function comments() { return $this->hasOne(Comment::class); }

D. public function comments() { return $this->belongsToMany(Comment::class); }

Solution

1. Step 1: Identify correct method for one-to-many

   In Laravel, hasMany() defines one-to-many relations.

2. Step 2: Match method to code

   public function comments() { return $this->hasMany(Comment::class); } uses hasMany(Comment::class), which is correct syntax.

3. Final Answer:

   public function comments() { return $this->hasMany(Comment::class); } -> Option B

4. Quick Check:

   hasMany() method syntax = public function comments() { return $this->hasMany(Comment::class); } [OK]

Hint: Use hasMany() to link one model to many [OK]

Common Mistakes:

• Using belongsTo instead of hasMany
• Using hasOne for multiple related models
• Forgetting to return the relationship

3. Given the following models, what will $post->comments->count() output if the post has 3 related comments?

class Post extends Model {
  public function comments() {
    return $this->hasMany(Comment::class);
  }
}

medium

A. 0

B. An error

C. null

D. 3

Solution

1. Step 1: Understand hasMany returns a collection

   The comments() method returns all related Comment models as a collection.

2. Step 2: Count related comments

   Calling $post->comments->count() counts the number of related comments. Since there are 3, it returns 3.

3. Final Answer:

   3 -> Option D

4. Quick Check:

   Related comments count = 3 [OK]

Hint: hasMany returns collection; count() gives number of related items [OK]

Common Mistakes:

• Expecting count() to return null
• Confusing count() with count property
• Assuming hasMany returns a single model

4. What is wrong with this hasMany relationship definition?

public function comments() {
  return $this->hasMany('App\Models\Comment');
}

medium

A. The method should return an array, not a relationship

B. hasMany should be replaced with belongsTo

C. The model class should be imported or use ::class constant

D. The method must be static

Solution

1. Step 1: Check model reference style

   Using a string for model class works but is discouraged; better to import and use Comment::class.

2. Step 2: Identify best practice

   Importing the model and using Comment::class avoids typos and enables IDE support.

3. Final Answer:

   The model class should be imported or use ::class constant -> Option C

4. Quick Check:

   Use ::class for model references [OK]

Hint: Use ::class for model names, not strings [OK]

Common Mistakes:

• Using string class names without import
• Confusing hasMany with belongsTo
• Making relationship methods static

5. You have a User model and a Post model. Each user can have many posts. How do you retrieve all posts for a user with ID 5 using Eloquent's hasMany relationship?

hard

A. $posts = User::find(5)->posts;

B. $posts = Post::where('user_id', 5)->get();

C. $posts = User::posts()->where('id', 5)->get();

D. $posts = User::find(5)->hasMany(Post::class);

Solution

1. Step 1: Use find() to get user by ID

   User::find(5) fetches the user with ID 5.

2. Step 2: Access posts via hasMany relationship

   Accessing ->posts returns all posts related to that user.

3. Final Answer:

   $posts = User::find(5)->posts; -> Option A

4. Quick Check:

   Retrieve related posts via user->posts [OK]

Hint: Find user then access posts property [OK]

Common Mistakes:

• Calling hasMany() directly on model instance
• Using where on User model instead of Post
• Trying to call posts() statically