[chaley]

Originally Posted by compurandom

The part of the original objection to this was that the columns cache calculated values. I figure that some templates are no worse than pulling the cached value, but have you noticed a performance difference with others?

I haven't noticed a performance difference because my library is too small. That said, I came to the conclusion that the composite column cache doesn't help enough to justify not adding the feature. When searching the cache is per book, so it helps only if a composite column is referenced directly or indirectly more than once in a query.

EDIT: What I said above is misleading. The cache is initialized for a book the first time that book is referenced, either in a search or by being displayed. It is cleared when data changes for a book. Thus repeated searches using non-template field references will use the cache.

Also, I've noticed that I can't sort one of my columns built from other columns, which makes me doubt how much caching is going on.

This usually happens when the search/sort type set in the column definition doesn't match the what the template produced.