|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Hi All
I'm working on a site for a friend and they want to include a discography of music releases. They need to enter details such as: Artist Album Name Track Names (linked to short excerpt) etc Is it better to have two tables linked via an ID (possibly album name). One table for Artist, Album etc and the other linked to this one via the Album name with the track names and links to the mp3's. Is it complicated to add/delete from multiple tables. Is this the best way of doing it? |
|
#2
|
|||
|
|||
|
you would definitly want to use multiple tables. Maybe even three.
tblArtist(artistID, ArtistName, Label) whatever you want for attributes tblAlumbs(AlbumID, AlbumName, ArtistID, Date) again more attributes you want tblTracks(TrackID, TrackName, AlbumID, ArtistID, Duration, TrackNumber ) ArtistID isn't required, but i think a fully normalized schema would include this here. I'm by no means a database guru, but I believe this is the fully normalized way to do it. Maybe someone else has more input. |
|
#3
|
||||
|
||||
|
imbrokn's table layout looks good to me except I don't think you need to have the ArtistID in the Tracks table b/c you can move through the Albums table to get it. The exception to this would be if you plan on using it when you have a Various Artists disk instead of using the artist "Various".
I've done this using the suggested layout with my modifications and it worked very well. |
|
#4
|
|||
|
|||
|
Thanks for the suggestions. Much appreciated.
|
![]() |
| Viewing: Dev Shed Forums > Databases > Database Management > database design comments appreciated |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|