Hi,
Il 12/03/2026 17:40, Maxime Gosselin ha scritto:
In Backslash PHP (the event sourcing framework I maintain), I had to
invent my own PdoInterface and a PdoProxy wrapper just to support lazy-
connect. A standard interface would have solved that problem. You can
see it here:
https://backslashphp.github.io/docs/application-setup/defining-services/
#configuring-the-pdo-connection <https://backslashphp.github.io/docs/
application-setup/defining-services/#configuring-the-pdo-connection>
I also maintain an internal enterprise application (Horizon) that has
grown over the years to include Laravel, Doctrine DBAL for migrations,
FluentPDO for query building, and other components depending on raw PDO.
Each manages or consumes a connection independently. /
PdoProviderInterface/ would be the common thread letting all of them
share the same managed connection. I cannot make this codebase public,
but I suspect it is not an unusual situation for applications that have
evolved organically.
I personally think this is a very specific problem of your application
that can be solved with an ad-hoc solution and/or through DI.
Cheers
--
Matteo Beccati
--
You received this message because you are subscribed to the Google Groups "PHP
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/php-fig/f3267933-2e0a-4580-872c-4f762b9f3bfb%40beccati.com.
