-
-
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
Added result caching for QueryBuilder #5539
Conversation
@twoleds please rebase your branch on top of |
db3846c
to
b13f970
Compare
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.
Looks good. Good work @twoleds! I'll let the PR hang for a bit more in case anybody has feedback.
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 there documentation to update?
Yeah, a section on caching could added to this document:
|
I provided some documentation for the query builder, but my English is not so good, please check it if I wrote it correct. |
bb591f8
to
47574ed
Compare
Thanks, @twoleds! |
Thanks for help to everyone, it was an interesting exprerience for me, I'm very happy that we have reached a successful end. Life will be a little bit easier. ❤️ |
This feature is so cool, thank you for your contribution @twoleds ! 👏 |
Summary
Added
enable/disableResultCache
method in QueryBuilder for result caching.I use
doctrine/dbal
in several projects and the result caching is annoying. Only way I can use result caching is callingexecuteCacheQuery
method inConnection
. I cannot usefetch*
methods inQueryBuilder
.I repeat this piece of code:
With this improvement it will be:
What do you think about it? Is it possible to implement something like that?