Tag: database
A performance anti-pattern where fetching N records triggers N additional queries — one per record — instead of a single JOIN.
2mo ago
database intermediate
N+1 Problem in Doctrine & Eloquent
PHP 7.0+
Accidentally issuing one query per related entity instead of one JOIN — the most common ORM performance pitfall, solved by eager loading.
3mo ago
performance intermediate
Issuing one query per row of a result set instead of a single JOIN — the most common database performance mistake in any ORM-based application.
3mo ago
database intermediate
Executing one query to get N records, then N more queries to fetch related data — one per record.
3mo ago
performance intermediate