petitminion Indeed… I wouldn’t bother to have this setting for all kind of libraries. If somebody is against this plz feel free to comment.
Well, we can at first build a setting that just checks all uploads and implement differentiation by library or later collection in a later stage.
petitminion Interesting idea. But considering this might might be used for the quality filter I think this would be a lost of processing time. Because if a filter is set we would need to do this query each time we request a tracks or a library information and this happens a lot.
You need to run a query anyways, and I don't think running a COUNT on a table is much slower then querying a field. Considering the field might be outdated all the time, I really prefer my proposition.
Some theory: Storing a derived value is basically a violation of database normalization. Of course there are always scenarios where such violations are valid. However, this needs to be well thought about and I'd prefer to test the sane way, in case its super slow we can always consider a workaround. For a discussion, check this StackExchange
