Performance: N+1 query problem (one query per row in a loop)
Code runs one query to load a list, then one more query per item — hundreds of queries per page.
too many queries Meaning
Not an error message, but the most common cause of slow pages and connection pool exhaustion with ORMs. Lazy-loaded relations accessed in a loop trigger a query each time.
Common causes
- Lazy relations accessed in loops/templates
- Missing eager loading (include/with/select_related/JOIN FETCH)
⚡ Quick fix
- Eager-load relations (Laravel with(), Django select_related/prefetch_related, Rails includes, EF Include)
- Log query counts per request in development
Detailed fix by platform
SQL
SELECT o.*, u.email FROM orders o JOIN users u ON u.id = o.user_id WHERE o.status = 'paid';
How to diagnose
- Count — Queries per request?
- Pattern — Same query repeated with different ids?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in SQL
Other ways to find it
Where this error sits
Origin: Data. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026