Weave Code
Doctrine Profiler Bundle Laravel Package
pixers/doctrine-profiler-bundle
Symfony bundle that enhances Doctrine profiling in the Symfony web profiler, letting you inspect executed SQL, bound parameters, timing, and backtraces to debug ORM and database performance.
Profile performance of your Doctrine's database queries
Frequently asked questions about Doctrine Profiler Bundle
- Can I use pixers/doctrine-profiler-bundle in a Laravel application?
- No. It is built as a Symfony bundle and depends on Symfony's bundle registration, dependency injection container, event dispatcher, and web profiler toolbar. Laravel has no bundle system, so there is no drop-in installation path. You would need to port the collector logic into a Laravel service provider or middleware.
- Does this bundle support Laravel Eloquent or only Doctrine ORM?
- Only Doctrine ORM and DBAL. It hooks into Doctrine query logging, not Eloquent. Laravel apps using Eloquent get no value from it, and even Laravel apps running Doctrine via laravel-doctrine/orm would need a custom integration.
- What are the best Laravel alternatives for query profiling?
- Use Laravel Debugbar for per-request query breakdowns, Telescope for historical and aggregate inspection, Clockwork, and DB::listen() for custom instrumentation. These are Laravel-native and actively maintained. For Doctrine in Laravel, DBAL middleware or a small custom collector is more appropriate.
- Is pixers/doctrine-profiler-bundle still maintained?
- No. The last release was September 2019, roughly six years stale, with no active issue triage. It expects PHP 7.x-era syntax and Symfony 2/3/4 APIs. Treat it as abandoned and be prepared to own a fork indefinitely if you adopt it.
- Which PHP, Symfony, and Doctrine DBAL versions does it support?
- Based on the 2019 release, expect PHP 7.x, Symfony 2/3/4, and Doctrine DBAL 2.x. DBAL 3 deprecated the SQLLogger interface and DBAL 4 removed it in favor of middleware. Running on PHP 8.2+, Symfony 6/7, or DBAL 3/4 would require a rewrite, not a version bump.
- How do I install and register the bundle in Symfony?
- In Symfony, install with Composer and register PixersDoctrineProfilerBundle in the kernel bundles array; the defaults enable the dedicated profiler panel. In Laravel this does not apply because there is no bundle registration or Symfony web profiler toolbar. You would have to reimplement the integration.
- Is it safe to enable this profiler in production?
- No. It is a development profiler tool designed for the Symfony debug toolbar and should not be enabled in production. It is also stale and unmaintained, so leaving it enabled adds unnecessary risk. Keep it local-only if you use Symfony at all.
- Does it show query parameters, timings, and backtraces?
- Yes. It collects executed queries, bound parameters and types, execution times, hydration details, and optional backtraces. It also highlights duplicate and slow queries to help spot N+1 and redundant calls. That data appears in its Symfony profiler panel, not in Laravel's toolbar.
- How hard is it to port this bundle to Laravel?
- Expect roughly 3 to 6 engineer-days to fork it, strip Symfony container and kernel listeners, remove Twig/toolbar templates, and re-expose the collector via a Laravel service provider, middleware, or DBAL middleware. That is often more work than writing a small query collector from scratch. Only pursue it if your Laravel app already runs Doctrine ORM and you specifically need the Pixers per-query breakdown view.
- Can I fork it and reuse the code under its license?
- Yes. It uses the BSD-3-Clause license, which is permissive and fork-friendly; reuse with attribution is allowed. Licensing is not a blocker, but you inherit all future patching and maintenance if you vendor or fork it.
Weaver
How can I help you explore Laravel packages today?