Advanced Eloquent Relations in Laravel: Key Insights from Chris Morrell at Laracon US 2025

August 9, 2025 (4mo ago)

Chris Morrell’s session at Laracon US 2025, “Advanced Eloquent Relations,” is a must-watch for any Laravel developer aiming to push the boundaries of what Eloquent ORM can do. He demonstrates that Eloquent relations are, at their core, just PHP code—meaning you can extend, customize, and even invent new types of relationships to solve unique business problems or data structures that don’t fit the usual conventions.

Core Takeaways

1. Eloquent Relations Are Just PHP Code

Under the hood, Eloquent relations are not magic—they’re simply query builders and PHP methods.
You’re not limited to the standard hasMany, belongsTo, etc. You can create custom relation classes to handle non-standard data models.

2. Custom Relations: When and Why

Legacy Data: Chris shows how to handle legacy databases, such as comma-separated IDs instead of pivot tables, by writing a custom relation that parses and matches these IDs.
Geospatial Relationships: You can define a relation (e.g., hasNear) that finds related models within a certain distance using latitude/longitude, leveraging raw SQL or custom PHP logic.
Dynamic/Generated Data: Relations don’t even have to hit the database. You can use Faker or even AI to generate related data on the fly for testing or demonstration purposes.

3. How Custom Relations Work

Implement two main methods: addEagerConstraints (set up the query for eager loading) and match (attach the loaded results to the parent models).
The interface is flexible: you can key, filter, and attach related data in any way you need.
This approach allows you to keep using Eloquent’s expressive syntax and features, even with unconventional data.

4. Practical Guidance

Follow Conventions First: 99% of the time, stick to Laravel’s built-in relations for clarity and maintainability.
Reach for Custom Relations When Needed: For the rare cases where business logic or legacy data require it, don’t be afraid to implement your own.
Document and Isolate: Clearly document custom relations and keep them isolated to avoid confusion for future maintainers.

5. Real-World Examples

HasSpeakers: Handles a list of speaker IDs stored as a string.
HasNear: Finds related models within a geographic radius.
HasFake/HasLetters: Generates fake or computed relations for demos or special cases.
HasPredictedEvents: Uses an AI model to predict and generate related event data dynamically.

How This Applies to My Work

At my work and in Laravolt, understanding the power and flexibility of Eloquent relations enables us to maintain clean code even when faced with legacy systems or unique business needs.
When building reusable components or open-source packages, knowing how to craft custom relations increases the adaptability and reach of our solutions.
For knowledge sharing and mentoring, these insights help junior developers see both the power and the boundaries of Laravel’s ORM.

References:

Advanced Eloquent Relations | Chris Morrell Laracon US 2025

Frequently Asked Questions

What are custom Eloquent relations in Laravel?

Custom Eloquent relations are user-defined relation classes that encapsulate non-standard data access patterns so you can keep using Eloquent's fluent, chainable API.

When should I build a custom Eloquent relation instead of using hasMany or belongsTo?

Create one only when legacy schemas, computed/virtual data, geospatial logic, or unconventional keying cannot be expressed cleanly with built‑in relations. Default to core relations first.

How do I implement a custom relation class in Laravel?

Extend Relation (or an existing relation), implement addEagerConstraints and match, and return a Relation instance from a model method so it plugs into eager loading, constraints, and serialization.

Can I eager load a custom relation?

Yes. If addEagerConstraints, initRelation, and match are implemented correctly, you can call with('myRelation') just like native relations, keeping N+1 queries under control.

How do I handle legacy comma-separated ID lists with Eloquent?

Parse the stored string into IDs inside a custom relation's constraints, run a whereIn query, then map results back in match—avoiding schema rewrites while keeping expressive model APIs.

How can I model geospatial or distance-based relations?

Write a relation that injects raw distance calculations (e.g. Haversine) or uses a spatial index extension, filtering by radius and ordering by computed distance in addEagerConstraints.

Can a relation return computed, fake, or AI-generated data?

Yes. A relation can hydrate arrays or DTOs into model-like objects without hitting the database, enabling demos, prediction features, or synthetic fixtures.

What performance considerations apply to custom relations?

Batch work in addEagerConstraints, avoid per-parent queries, cache expensive derived datasets, and prefer database-side filtering over in-PHP loops to prevent hidden N+1 issues.

How do I test a custom Eloquent relation?

Write unit tests asserting the relation returns expected collections, respects eager loading counts, and does not increase query count when loading multiple parents. Use assertDatabaseQueryCount helpers if available.

What are common pitfalls with custom relations?

Missing match logic, per-model queries, leaky abstractions mixing business logic, and unclear naming. Always document intent and verify eager loading reduces queries.

Do custom relations serialize and work with API resources?

Yes—once matched onto the model they behave like native relations for toArray(), JSON resources, and lazy/eager loading, provided you return Collections or model instances.

How should teams document and maintain custom relations?

Centralize them in a dedicated namespace, add PHPDoc usage examples, explain data shape & constraints, and link to architectural decisions to reduce onboarding friction.