Hello users and devs,

I posted a few months ago about how I thought amarok\'s DB model should be different and all of that. By that time a few devs told me that changing it was not a priority. Well, during the semester I couldn\'t find some time to just make a proposal, but I finally could do it today (thank god for Summer Vacations, though it\'s winter in Brazil). So today I drew up a little diagram of my idea (wich is fairly simple). it\'s on http://www.ic.unicamp.br/~ra009663/amar ... estion.jpg [jpeg], and the .dia is on the same place, just change the extension. (supposing anyone wants to tweak it). Well I\'d like your oppinions on this, \'cause I really want special id3v2 tags (composer, original album...) and Multiple {Artist, Genre} support and would like to contributte a patch. But I wouldn\'t want to waste my time doing something that nobody is gonna want to use

The biggest problem I see with this approach is how to tell different albums with the same name from each other. We could, of course, correspond album+artist and use that as the key for images and all (which is, I think, what you currently do)... I can\'t think yet of a perfect answer... I\'d like to take as many suggestions as possibles...

If anyone survived this huge post, thanks in advance for the attention and help... waiting for oppinions

MusicBrainz ID\'s are perfect for indicating albums.

But that\'s only good for those of us who actually take the time to properly tag files.

The person with the 4000+ kazaa-downloaded MP3s from random artists, all in one directory... eh, they get what they deserve... :evil:

So some info is in the Song table and other stuff is spread out in other tables?

I don\'t get it.

The info that is unique to each song is in the songs table. That is filename, track length, song title and so on. The other info (artist, album, genre) each has its own table and you have tables that express relations. For example, you have a Song x Artist table. So you\'re not limited to what you can put in a text field, you can have as many artists as you want for a given song (same for other desirably multiple tags). In addition, say you now want to support the composer tag. Then you just add the Song x Composer table, and the code to handle it. DB\'s are still compatible, and you don\'t waste the space of the field on all those songs that aren\'t that well tagged....