Why this lesson matters

Understand eloquent relationships and apply it in a small Laravel feature. Migrations define database evolution, Eloquent models represent records and relationships, and queries should preserve the integrity constraints the schema is designed to enforce.

How to reason about it

  • For Eloquent Relationships, the outcome to verify is: A model relationship represents a domain fact, not just a query shortcut.
  • In Eloquent Relationships, keep this failure controlled: Relying only on application validation while omitting database keys, foreign keys or appropriate column types leaves integrity vulnerable to other writers.
  • Eloquent Relationships practice target: Create a parent and child table with a foreign key, model the relation in Eloquent, insert data and query it through the relationship.
Diagram

User to orders relation

Practical walkthrough

In the Eloquent Relationships walkthrough: A model relationship represents a domain fact, not just a query shortcut.

app/Models/User.phpphp
public function orders(): HasMany
{
    return $this->hasMany(Order::class);
}

Practice it yourself

Practice

Eloquent Relationships exercise

Create a parent and child table with a foreign key, model the relation in Eloquent, insert data and query it through the relationship.

  • Record the expected result before execution
  • Test one valid path and one lesson-specific failure path
  • Explain in two lines which boundary owns the decision

Summary