>It would need to be something like:
>
>WHERE genre IN (1,6,7,8) AND genre NOT IN (2,3,4,5,9,10)
>
Effectively, what you are suggesting is that the user chooses what genres to
exclude from random play, instead of choosing what genres to include. I don't
think you need both where genre IN (...) and genre NOT IN (...), only the NOT
IN clause, as obviously the only genres left after excluding some, are the ones
you want to include ;-)
Would this affect performance? If I have say 100 genres, and I untick them all
and tick "Rock", in the past it would have a single clause WHERE genre IN
('Rock'), but with this change it would become WHERE genre NOT IN (list of 99
genre id's).
There would be another iffy side effect of this change; some songs may be
excluded where another unintentional genre is deselected.
For example, I often tag songs with a main genre, such as Rock, and then other
descriptive genres, such as Live, Acoustic and Xmas.
If I select Rock and deselect everything else, that would mean that it would
not select any Live, Acoustic or Xmas songs. So I think a user would need to
select all genres by default, and choose the ones they are not interested in
hearing, which could be quite arduous.
A cleaner interface may be to have tri-state values, or a choice to pick a list
of genres to include, and a list to exclude. A single list of include/exclude
genres is going to confuse.
Phil
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
