Updated: Comment #10
Too many caches are generated in table cache_views_data in the following case:
- a Views view with more then one display,
- and caching enabled,
- and each display/several displays having the same result, but a different output (e.g. chart and table)
For a complicated view, the results cache and the output cache save notable time.
If a user switches between displays, there is no need to fetch the database data again, if it is already stored in the results cache.
Below is a patch that eliminates querying the database a second time, when switching between displays of the same query.
is a prerequisite, since that issue makes sure the cache key is built correctly.
The display name is discarded from the output key name. This might be a problem in some cases, but IMO only serves documentation purposes.