Replies: 2 comments
-
Absolutely agree, so what you're saying is that when the entry within a cache is saved, the cache is then regenerated automatically in the background as a task. Therefore not putting the load on the user who next visits the page and has to wait a long time for the database query to run. |
Beta Was this translation helpful? Give feedback.
-
This would be very useful when working with large datasets. We have a map with over 1,000 Entries plotted on it, and it takes 30s+ to generate the initial cache result. |
Beta Was this translation helpful? Give feedback.
-
I'd like to be able to pass a parameter to the
{% cache %}
tag — something like{% cache lazyrebuild %}
which would immediately return the cached version, but off in a task on the backend, it’d be rebuilding the data in the cache tag pair if it was invalidated due to an Element contained within it that changed.This allows the front-end to always be responsive to the user, but also kicks off the rebuilding of the cache.
Beta Was this translation helpful? Give feedback.
All reactions