-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove Abstraction\Result #4294
Conversation
@@ -5,7 +5,8 @@ | |||
use Doctrine\Common\Cache\Cache; | |||
use Doctrine\DBAL\Driver\Exception; | |||
use Doctrine\DBAL\Driver\FetchUtils; | |||
use Doctrine\DBAL\Driver\Result; | |||
use Doctrine\DBAL\Driver\Result as DriverResult; | |||
use Doctrine\DBAL\Result; |
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.
Is having a Doctrine\DBAL\Result
in $result
on purpose instead of a Driver\Result
and planned for 3.0?
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.
Yes. The caching layer only works with the wrapper-level result. Prior to this change, the wrapper result would implement the driver result interface, so this signature would work. As of this change, it's no longer true.
Additional references:
- The same is true for the wrapper Connection and Statement classes as of Do not implement driver-level interfaces by wrapper-level classes #4159.
- We may rework the caching layer into a driver-level middleware where it belongs but it's not a top priority for me. See Rework the portability layer to act as a middleware #4157, there's basically a similar issue here.
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.
If the answer to my previous question is "yes", this then this is ready for merge IMO.
5b38026
to
4f57b1d
Compare
4f57b1d
to
496bd71
Compare
The interface is proposed for deprecation in #4291.