View Single Post
Old 01-05-2023, 10:40 AM   #452
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,529
Karma: 8075938
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by ownedbycats View Post
Thanks.

When using first_non_empty, is there any performance difference between checking a default and custom column? Trying to figure out the optimal order for this (e.g. the more complex ones with multiple checks at the end).
Fetching a custom column is nanoseconds slower than fetching a standard column. Certainly not enough to worry about.

The first_non_empty() conditions should be ordered by likelihood. Put the ones first that are most likely to match, regardless of complexity.
chaley is offline   Reply With Quote