2006-03-04, 02:31
ah. that's not possible at the moment. the only history kept is a rolling list of the last 25 songs to prevent duplicates within that window. i've been considering using a database table as the history in order to reduce memory.
i dont know how feasible this is, but i was thinking about using a table thats dropped and created everytime party mode is enabled in order to explicitly clear it. then as songs are picked, their id's would be pushed into this table. getting the total number of unique songs from this table would be trivial. then picking songs without repeats can be accomplished using a nested query, something like this:
select * from songview where songview.idsong not in (select partymode.idsong from partymode order by partymode.rowid desc limit 25)
i dont know how feasible this is, but i was thinking about using a table thats dropped and created everytime party mode is enabled in order to explicitly clear it. then as songs are picked, their id's would be pushed into this table. getting the total number of unique songs from this table would be trivial. then picking songs without repeats can be accomplished using a nested query, something like this:
select * from songview where songview.idsong not in (select partymode.idsong from partymode order by partymode.rowid desc limit 25)
