A common use case is to have views that pertain to one type of documents. I have users that freak out because they don't see the stuff they just submitted.

As far as caching scenarios go, it would be cool if views caches could get invalidated as soon as the data changes, according to simple heuristics: e.g., if a view is related to some document types, invalidate the cache as soon as some change occurs in a document of the given type. This could be a cache option.

On the site I'm working with, documents are heavily typed (I have about 10 distinct types), and there's one type which is very frequently consulted, but seldom changed, and changes should occur about instantly... so I can't really set caching, and I incur some performance hit.

Comments

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

You will have to implement a custom caching plugin to handle this feature. Views' built-in caching is time-based only.