2814 - numeric support for custom columns

[Barry4679]

So pleased to see this added. Thanks.

Comments:

1. you clear the comparison value if I toggle the criteria operator. Steps:
   • set operator to =, and comparison value as 6
   • change the operator to >=
   • ===> the comparison value is cleared ?
2. string comparison with new operators is sometimes incorrect; examples where the tag custom date (string) value is 2023/05/12
   • = 2023/05/12 ==> True
   • <= 2023/05/12 ==> False ... unexpected
   • >= 2023/05/12 ==> True
   • > 2023/05/11 ==> True
   • < 2023/05/11 ==> False
   • > 2023/05/13 ==> True ... unexpected
   • < 2023/05/13 ==> False ... unexpected

Can these issues be fixed please?

[Ludek]

Hi Barry,
could you please specify what do you mean by
<= 2023/05/12 ==> False ... unexpected

Maybe attaching a screenshot would help to understand how exactly you are testing and which rules you applied.

Thanks!

[Barry4679]

could you please specify what do you mean by
<= 2023/05/12 ==> False ... unexpected

The track has the string 2023/05/12 stored in a Custom column
I setup an autoplaylist where criteria for the custom column was <= 2023/05/12

My expectation was that the track would be included in the playlist, because the operator was <=, and the value was equal

The track was not included in the playlist ... which was "unexpected"

You understand, or do you need screenshots?

BTW .. maybe this is relevant:

• I had renamed the Custom column from Custom4 to Album Played, using Tools|Options|Library|Fields|RenameCustomFields

• Note the embedded blank

• I designed the AutoPlaylist using my custom name for the column

[Ludek]

I see, this is because of the SQL constructed as

Code: Select all

SELECT Songs.*  FROM Songs  WHERE CAST(Songs.Custom1 AS INT)>2023/05/12 AND (Songs.Custom1 <> '' ) 

where '/' is actually a division operator.

To be fixed as https://www.ventismedia.com/mantis/view.php?id=20222