You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a new deprecation in Doctrine DBAL 3.2+ (released a few days ago).
Work is in progress in DoctrineBundle to migrate to the new way. See doctrine/DoctrineBundle#1431 and doctrine/DoctrineBundle#1429 for the work to migrate away from the SQLLogger interface (the DbalLogger class itself won't be changed to stop using the interface, but it will be deprecated in the future once dropping support for older DBAL versions)
…Logger (l-vo)
This PR was merged into the 5.4 branch.
Discussion
----------
[DoctrineBridge] Allow to use a middleware instead of DbalLogger
| Q | A
| ------------- | ---
| Branch? | 5.4
| Bug fix? | no
| New feature? | yes
| Deprecations? | no
| Tickets | Step toward the fix of doctrine/DoctrineBundle#1431 (mentioned too in #44313 and #44495)
| License | MIT
| Doc PR |
The SqlLogger that is used in doctrine bridge and doctrine bundle has been deprecated and replaced by a system of Middleware.
A work has started on Doctrine bundle with doctrine/DoctrineBundle#1456 and doctrine/DoctrineBundle#1472
This PR suggest to add a middleware thats covers what was previously done by `DbalLogger` and `DebugStack`.
Another PR will follow in DoctrineBundle for the integration.
Commits
-------
20d0806 Allow to use a middleware instead of DbalLogger
Symfony version(s) affected
6.0.0
Description
I Use Symfony 6.0 and profiler show
Deprecations
in all pages:How to reproduce
Read description ...
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: