-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Lock] Use platform to identify the PDO driver #43281
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
Conversation
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.
This PR revert what have been done in 7eca3a5#diff-98857ac5bb047b333495db5092ea4b875924022056c5b5522d7ecb224fac5f6f
@nicolas-grekas do you remember why you changed this in a merge commit?
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.
Regarding the @derrabus comment, this PR brings nothing but introduce a future deprecation for upcoming Doctrine 3.2
I'm 👎 for this change
edit: this PR fixes the issue referenced in the description
@jderusse this PR fixes compatibility with driver decorators (inspecting the driver class to find the target platform is a mistake). See the ticket referenced in the issue description, which describes precisely such a bug. |
Still.. |
I agree, seems worth trying to fix this using |
I've changed the approach to use the |
824ffc7
to
687a7ed
Compare
Thank you @Jean85. |
This should fix the issue in the same way we did for #42011. I'm not sure if I should add/change any test...