N+1 Problem in Doctrine & Eloquent

Also Known As

TL;DR

Explanation

The N+1 problem: fetching N orders then calling $order->customer inside a loop fires N additional queries — one per order — instead of a single JOIN. In Doctrine: use DQL JOIN FETCH or addSelect on a QueryBuilder to eager-load associations. In Eloquent: use with('customer') on the query. Detect N+1 in development with Laravel Telescope, Debugbar, or Clockwork (all show per-request query counts). In Doctrine enable SQL logging to a file. A page making 300 queries that should make 3 is the signature. Fix: identify the loop, move the JOIN upstream, verify query count drops. For deeply nested associations, consider a dedicated read-model query bypassing the ORM entirely.

Common Misconception

Why It Matters

Common Mistakes

• Not enabling ORM query logging in development — N+1 queries are silent without it.
• Lazy-loaded relationships in loops — the classic ORM N+1 pattern.
• Using with() for eager loading but then accessing a non-eager-loaded relationship inside the loop.
• Not using tools like Laravel Debugbar or Symfony Profiler to detect query counts per request.

Code Examples

$orders = $em->findAll(Order::class); // 1 query
foreach ($orders as $o) {
    echo $o->getCustomer()->getName(); // N queries!
}

$orders = $em->createQuery(
    'SELECT o, c FROM Order o JOIN FETCH o.customer c'
)->getResult(); // 1 query

References

• ↗ https://www.doctrine-project.org/projects/doctrine-orm/en/current/reference/dql-doctrine-query-language.html#joins

Tags

Related Terms