View Single Post
Old 08-30-2010, 01:02 PM   #16
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,476
Karma: 8025702
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by Starson17 View Post
2) I may decide I need an #award2 and an #award3 column for overlaps. It would complexify searching, however.
A thought: I don't think it would be hard (more than an hour of work) to add searching of the form #foo*:query, where #foo* means any custom field beginning with foo. This would dramatically simplify your #award[1-5] search problem. Of course, the query would need to be valid for all the matched fields, but all that would happen if it isn't is the query would fail.

The gotcha might be using them (award1, award2, etc) in save templates. Not sure if this is an issue.

Of course, the right solution would be 'series is_multiple=True', but that isn't going to happen.
Quote:
As an aside, your custom columns are incredibly useful, even where I also have the data in tags.
Thanks.
chaley is offline   Reply With Quote