Quote:
Originally Posted by aleyx
That solution does store the needed data correctly, but doesn't help when you want to actually use that data (i.e. in searches, filters, templates, etc) without adding max(series_*) fields, where series_* are the custom columns added.
Several use cases come to mind, but mostly short stories collections where two or more works are side-stories in their respective series. Looking for "My Series" would look like
Code:
series:"=My Series" or series_1:"=My Series" or series_2:"=My Series" or series_3:"=My Series" or series_4:"=My Series"
That would work of course, but at the cost of legibility and maintainability. Same with column colors/icons, etc. |
You can solve the searching problem using grouped search terms (preferences / searching). They let you combine multiple columns into one virtual column.
Coloring and icon rules would require a different solution, probably a tags-like composite column that aggregates the names from the columns included in the search term. Hmmm... I could make a template function that returns the values in the "virtual" column. This would be a gui-only function so it would not obviate the need for the composite column if the info is to be used in save-to-disk templates.
I am not sure what problem you are solving with the max() function.