Quote:
Originally Posted by chaley
This doesn't work. There are characters such as plus and parentheses that sort before period. The suggested change ensures that periods become something that sorts before all other printable characters.
Adding a "sort" would indeed permit people to do what they wanted with order but I think it is impractical. Tags and tags-like items come and go frequently, so maintaining the sort would be time consuming. It is also a database-incompatible change, which would break any plugin or app that thinks it knows the database schema.
The change I made is similar to the one suggested -- ensure that X.Y sorts below Xanything.Y. There was no need to change the value of the tag other than when computing the "sort key", and this only when the column is hierarchical. Templates etc don't need to be updated unless they depend on order, which isn't easy to do.
|
Right, that's why I suggested the change as I did, to be as minimally invasive as possible. It's not a zero-cost change, but I think it fairly small and limited scope. Ideally it happens in basically one place, whereas if I understand the other proposal it would have broader reach.
The change I really want is to be able to specify my own tag and hierarchy delimiters (comma and period both happen in real strings!) but that's a much scarier change.
(Another one I'd like, also intended for use with tags and hierarchies, is the option in the bulk regex editor to say "if the tag doesn't match the RE, remove it"... AKA "if you find a tag like this, change it in this way, else remove it". It would be very useful when the tags contain metadata I want in another field, but it might be entirely a 'me' problem.)