Why Polymorphic relationships in Laravel? - Purpose & Use Cases

The Big Idea

Discover how one table can handle many relationships without messy code!

The Scenario

Imagine you have a blog where users can comment on posts, photos, and videos. You try to create separate comment tables for each content type.

The Problem

Maintaining multiple comment tables is confusing and repetitive. Adding a new content type means creating new tables and code everywhere.

The Solution

Polymorphic relationships let you use one comments table for many content types, linking comments to posts, photos, or videos easily.

Before vs After

✗ Before

comments_post table, comments_photo table, comments_video table with separate queries

✓ After

comments table with commentable_id and commentable_type columns, single query to fetch comments for any content

What It Enables

You can manage comments for many different content types with one simple, flexible database design.

Real Life Example

A social media app where users comment on posts, photos, and events all stored in one comments table.

Key Takeaways

Polymorphic relationships reduce database complexity.

They let one table relate to multiple models easily.

Adding new related content types becomes simple and clean.

Practice

1. What is the main purpose of polymorphic relationships in Laravel?

easy

A. To allow a model to belong to more than one other model on a single association

B. To create many-to-many relationships between two models

C. To enforce strict foreign key constraints in the database

D. To automatically generate database migrations

Solution

1. Step 1: Understand polymorphic relationships

   Polymorphic relationships allow a model to belong to multiple other models using a single association.

2. Step 2: Compare with other relationship types

   Unlike many-to-many or one-to-many, polymorphic lets one model relate to different models without separate foreign keys.

3. Final Answer:

   To allow a model to belong to more than one other model on a single association -> Option A

4. Quick Check:

   Polymorphic relationships = single association to multiple models [OK]

Hint: Polymorphic = one model relates to many different models [OK]

Common Mistakes:

• Confusing polymorphic with many-to-many relationships
• Thinking it automatically creates migrations
• Assuming it enforces database constraints

2. Which method should you use in the related model to define a polymorphic relationship?

easy

A. morphTo()

B. hasMany()

C. belongsToMany()

D. morphMany()

Solution

1. Step 1: Identify the related model method

   The related model uses morphTo() to define the polymorphic inverse relationship.

2. Step 2: Differentiate from owning model methods

   Owning models use morphMany(), but the related model uses morphTo().

3. Final Answer:

   morphTo() -> Option A

4. Quick Check:

   Related model uses morphTo() [OK]

Hint: Related model always uses morphTo() for polymorphic [OK]

Common Mistakes:

• Using morphMany() in the related model
• Confusing belongsToMany() with polymorphic
• Using hasMany() instead of morphTo()

3. Given the following code, what will $comment->commentable->name output?

class Comment extends Model {
  public function commentable() {
    return $this->morphTo();
  }
}

$comment = Comment::find(1);

Assuming the comment belongs to a Post with name = 'Laravel Tips'.

medium

A. Error: Undefined property 'name'

B. 'Laravel Tips'

C. null

D. 'Comment'

Solution

1. Step 1: Understand morphTo() behavior

   The commentable() method returns the related model instance, here a Post.

2. Step 2: Access the related model's property

   Accessing name on the Post model returns 'Laravel Tips'.

3. Final Answer:

   'Laravel Tips' -> Option B

4. Quick Check:

   commentable->name = 'Laravel Tips' [OK]

Hint: morphTo() returns related model instance [OK]

Common Mistakes:

• Expecting null if not eager loaded
• Confusing property with method call
• Assuming error without checking model relation

4. What is wrong with this polymorphic relationship definition?

class Image extends Model {
  public function imageable() {
    return $this->morphMany();
  }
}

medium

A. morphMany() requires parameters but none are given

B. No relationship method is needed in Image model

C. The method name should be morphable()

D. The method should be morphTo(), not morphMany()

Solution

1. Step 1: Identify the model role

   Image is the related model, so it should use morphTo() for polymorphic inverse.

2. Step 2: Check method used

   morphMany() is for owning models, not related models.

3. Final Answer:

   The method should be morphTo(), not morphMany() -> Option D

4. Quick Check:

   Related model uses morphTo() [OK]

Hint: Related model must use morphTo(), not morphMany() [OK]

Common Mistakes:

• Using morphMany() without parameters
• Wrong method name for polymorphic inverse
• Thinking no method is needed

5. You want to create a polymorphic relationship where both Post and Video models can have many Comment models. Which of the following is the correct way to define the relationship in the Post model?

hard

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

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

C. public function comments() { return $this->morphMany(Comment::class, 'commentable'); }

D. public function comments() { return $this->morphTo(Comment::class, 'commentable'); }

Solution

1. Step 1: Identify owning model relationship

   Post owns many comments via polymorphic relation, so use morphMany().

2. Step 2: Use correct parameters

   morphMany() requires the related model class and the polymorphic name 'commentable'.

3. Final Answer:

   public function comments() { return $this->morphMany(Comment::class, 'commentable'); } -> Option C

4. Quick Check:

   Owning model uses morphMany() with polymorphic name [OK]

Hint: Owning model uses morphMany() with polymorphic name [OK]

Common Mistakes:

• Using hasMany() instead of morphMany()
• Using morphTo() in owning model
• Using belongsToMany() for polymorphic