>If the SBS database has such a category as "No album", how about not >assigning tracks in that category any album year value, just a track >year value? In that case I would say that the TORY value (normally the >original year) should take precedence over the TYER value (normally >release year, which is generally associated with the whole album). > "No Album" is a row in the album table - it's not a category.
The scanner will put a single year value against each song (in tracks.year), and then some logic decides what the albums.year value should be. albums.year must have a value (it's not nullable), and thus if the logic decides that there's no year (e.g. first song on the "album" has no year), then it stores albums.year=0. Looking in my database, the album "No Album" has year=0, and appears under Browse Years > Unknown. There are 620 songs listed on that "No Album" in this way, but I actually have 1,984 songs with album=No Album (the majority have a year). I can't browse to a specific year to see the "No Album" songs for that year, because it only sees one arbitrary value for the album year. Genres work differently - if I have an album with songs having different genres, I can browse to each genre and see those songs. i.e. it doesn't consider an arbitrary genre to be the album genre - there is no album genre, it's worked out on the fly based on the tracks that match the query. _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
