Reimplementation of the SQLLogger
A replacement for the the former Doctrine DBAL SQLLogger
Doctrine\DBAL\Logging\SQLLogger was deprecated. The bundled Middleware-based replacement is similar, but with a few critical differences:
- It's tied directly to a PSR-3 logger
- The log format (and levels) is part of the middleware; it cannot be customized
- There is no event for queries completing; this makes it impossible to use the logger for application telemetry.
QueryLogger API remains the same:
Doctrine\DBAL\Logging\SQLLogger is now
Firehed\DbalLogger\QueryLogger (the API remains the same).
Setup for DBAL/ORM is different; that's inherent to the deprecation that prompted the creation of this library.
The port of the original SQLLogger did not have native return types, instead favoring docblocks. This adds an explicit return type to the interface.
There's a new
DbalLogger interface which your logger can also implement, creating hooks for
This is optional, and if you want a low-effort conversion, it's fine to stick with the basic
SAVEPOINT queries either will show up in their underlying connection-specific syntax or possibly not at all.
I'm not sure how to test this!
(doctrine/dbal/src/Connection.php and thereabouts)
If you have an implemenation of the DBAL SQLLogger interface (which is probably the case if you're here), you'll need to make the following changes:
- Have it implement
- Wrap it in Middleware:
$middleware = new Firehed\DbalLogger\Middleware($yourQueryLogger);
- Adjust your DBAL/Doctrine setup code to use the Middleware instead of directly using the Logger:
If you don't have a SQLLogger implementation you're looking to migrate, you'll want create one!
- Wrap it in a middleware:
$middleware = new \Fireheed\DbalLogger\Middleware($instanceOfYourClass);
- Add it to the DBAL/Doctrine config, per above.
That should do it!
This project follows semantic versioning.
Please use Github for reporting any issues or making any feature requests.