by MisterFlix » Wed Feb 15, 2023 8:32 am
Peke wrote: ↑Tue Feb 14, 2023 5:24 pm
It would be time and resource consuming to add it as criteria due the fact that it would need to be calculated each time window refreshes.
Admittedly, I don't know how exactly MM's database is structured, but wouldn't it be possible to recalculate the value of an album only if a rating within it changes, and then save that in a new db field for albums (or the album's tracks, whichever makes more sense)? Heck, this could even be optional, although I doubt that this will suck much of the computing power.
And yes, as Barry4679 pointed out, even if it is a calculation that has to be done every time the view is opened (is there no caching?), that would be at the behest of any users who wishes to use that particular filter.
[quote=Peke post_id=506508 time=1676413484 user_id=213]
It would be time and resource consuming to add it as criteria due the fact that it would need to be calculated each time window refreshes.
[/quote]
Admittedly, I don't know how exactly MM's database is structured, but wouldn't it be possible to recalculate the value of an album only if a rating within it changes, and then save that in a new db field for albums (or the album's tracks, whichever makes more sense)? Heck, this could even be optional, although I doubt that this will suck much of the computing power.
And yes, as Barry4679 pointed out, even if it is a calculation that has to be done every time the view is opened (is there no caching?), that would be at the behest of any users who wishes to use that particular filter.