Yes, I know that. I did read the book. But that action makes heavy queries to the database, so, if I just cache the listing of the data I'm getting, I will be executing always those heavy queries... that is the reason I was caching the action.
On Apr 24, 5:13 pm, Eno <[email protected]> wrote: > On Fri, 24 Apr 2009, HiDDeN wrote: > > Eno, what you are recommending is to cache parts of the template. I > > need to cache the action as well. > > But you need the action to run as well. You can't have it both ways - > either you run the action or you dont. The only way you can get the action > to run every time is to NOT cache it; intead you cache partials and > fragments of the template. > > Seehttp://www.symfony-project.org/book/1_2/12-Caching#chapter_12_sub_cac... > where it says: > > "Action caching applies to only a subset of actions. For the other > actions--those that update data or display session-dependent information > in the template--there is still room for cache improvement but in a > different way. Symfony provides a third cache type, which is dedicated to > template fragments and enabled directly inside the template. In this mode, > the action is always executed, and the template is split into executed > fragments and fragments in the cache, ..." > > -- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
