View Single Post
Old 07-10-2012, 06:59 AM   #542
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,499
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by JimmXinu View Post
If that's the official solution, I can certainly live with it.

But it would have been a lot easier to find if the behavior were consistent, either one way or the other.

A simple custom column and a composite column with a simple template ("{#characters}, {#genre}"): both work without the refresh.

But a composite column with a template function ("{#genre:uppercase()}") doesn't work without the refresh.
I found an easy & efficient way to make composite columns refresh when "normal" columns are changed, satisfying your consistency goal. The change is in trunk source and will be released this week.

You should no longer need to do the refresh_ids before calling get_metadata. It doesn't hurt anything if you continue to call it.
chaley is offline