Runtime Analysis Tool for Doctrine ORM — Integrated into Symfony Web Profiler
Why Runtime Analysis?
Unlike static analysis tools (PHPStan, Psalm) that analyze code without execution, Doctrine Doctor:
- Detects runtime doctrine issues by analyzing real execution context (actual parameters, data volume, query plans), including N+1 queries, real query performance bottlenecks, and missing indexes.
- Integrated into your workflow: Results appear directly in Symfony Web Profiler during development
- 📍 Backtrace: Points to exact template line
- 💡 Suggestion: Use
->addSelect(..)to eager load products
- Performance — Detects N+1 queries, missing database indexes, slow queries, excessive hydration, findAll() without limits, setMaxResults() with collection joins, too many JOINs, and query caching opportunities
- Security — Identifies DQL/SQL injection vulnerabilities, QueryBuilder SQL injection risks, sensitive data exposure in serialization, unprotected sensitive fields, and insecure random generators
- Integrity — Detects cascade configuration issues, bidirectional inconsistencies, missing orphan removal, type mismatches, float usage for money, uninitialized collections, EntityManager in entities, and architectural violations
- Configuration — Validates database charset/collation settings, timezone handling, Gedmo trait configurations, MySQL strict mode, and other database-level configurations
Step 1: Install
composer require --dev ahmed-bhs/doctrine-doctorStep 2: That's it!
Auto-configured via Symfony Flex. No YAML, no configuration files needed.
Step 3: See it in action
- Refresh any page in your Symfony app (in
devenvironment) - Open the Symfony Web Profiler (bottom toolbar)
- Click the "Doctrine Doctor" panel 🩺
Configure thresholds in config/packages/dev/doctrine_doctor.yaml:
doctrine_doctor:
analyzers:
n_plus_one:
threshold: 5 # default, lower to 3 to be stricter
slow_query:
threshold: 100 # milliseconds (default)Enable backtraces to see WHERE in your code issues originate:
# config/packages/dev/doctrine.yaml
doctrine:
dbal:
profiling_collect_backtrace: trueFull configuration reference →
| Before — 100 queries | After — 1 query |
$users = $repository->findAll();{% for user in users %}
{{ user.profile.bio }}
{% endfor %} |
$users = $repository
->createQueryBuilder('u')
->leftJoin('u.profile', 'p')
->addSelect('p')
->getQuery()
->getResult(); |
|
Doctrine Doctor detects the N+1 pattern at runtime — reports query count,
execution time, points to the exact template line, and suggests eager loading with |
|
| Document | Description |
|---|---|
| Full Analyzers List | Complete catalog of all 66 analyzers covering performance, security, integrity, and configuration - find the perfect analyzer for your specific needs |
| Architecture Guide | Deep dive into system design, architecture patterns, and technical internals - understand how Doctrine Doctor works under the hood |
| Configuration Reference | Comprehensive guide to all configuration options - customize analyzers, thresholds, and outputs to match your workflow |
| Template Security | Essential security best practices for PHP templates - prevent XSS attacks and ensure safe template rendering |
See Contributing Guide for guidelines.
MIT License - see LICENSE for details.
