start of new DB design

[Ian Monroe]

Attached is my first crack at redesigning the database for Amarok 2.0.
I used the demo version of theKompany.com's Data Architect (though it
has no limitations that I could see) to do it. Its not the best piece
of software, but at least it doesn't start going wacky like
Umbrello...

Known problem: currently the 'trackid' primary key is in the 'urls'
table, which is why everything is pointed to it. It makes more sense
to put it in the 'tracks' table, since thats where all the info is.

I added a playlistcurrent table, and a set of tables to handle
undo/redo. There are two types of tracks that can be in a playlist,
those that are part of the collection and those that are not. So
either trackid or externalid in playcurrent goes unused (externalid is
a FK for the PK of playlistexternal, I just noticed the latter is
missing.) This creates more complications in the undo/redo system.

Any other ideas on how to handle that?

Other then that, I'm looking for some general feedback on what people
think of it. I left podcast stuff alone, I'm not sure if people think
it needs some work or not. Amazon is fine and simple as it is.

Peace,
Ian Monroe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amarokdb_2_1.pdf
Type: application/pdf
Size: 36112 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20070606/9d7c100a/attachment-0001.pdf 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amarok21.MYModel.bz2
Type: application/x-bzip2
Size: 10659 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20070606/9d7c100a/attachment-0001.bz2