-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the compatibility layer for Doctrine DBAL to avoid side-effects of polyfilling #553
Conversation
7745826
to
b9c21c9
Compare
After thinking again about this, and while we have some clear advantages of splitting the implementation into two, e.g. the fact that we can add typehints to more things and evolve the two classes independently without worrying about keeping the compatibility with both major versions at the same time, I'm pretty sure this does not solve #483 and there is no way to solve it. Basically, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍 splitting is surely a better approach.
Maybe we should declare those implementations @internal
?
d6c63b2
to
91b3320
Compare
Yes, that's a good idea! |
I got an E_WARNING: Stack trace |
This PR fixed it already I guess #552 |
#552 is released as 4.2.3, you can test it out. |
This is an attempt at fixing #483 and #484. I decided to split the
TracingDriver
class into two versions, each compatible with just one of the major versions of Doctrine DBAL we support (2.x
and3.x
)