Quote:
Originally Posted by eschwartz
Hence answer #1, which I have seen Kovid give numerous times (every time someone asks for the series column to support multiple series').
|
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.
Quote:
Originally Posted by eschwartz
And also a confusing bone to pick with floats as the datatype.  |
Yeah, I don't really understand either. For my part, beside the formatting point davidfor made, I'd think that Python's distutils.version would make more sense and be more flexible. But I guess perfs would take a non-negligible hit.
N.