jaymc Posted September 21, 2006 Share Posted September 21, 2006 Ok, I am making a music website.Each song info will be stored in a database, I am thinking of using the following fields for the songs table[b][ID] [GENRE] [ARTIST FULL NAME] [ALBUM NAME] [SONG NAME] [ALBUM ID] [VIEWS][/b]Now their is going to be about 300 albums, so if their are 15 songs per album then thats 4500 rows in the tableThe query will be pretty straiight forward when someone wants to listen to a song, it will be selected by ID which will be uniqueAnyway, Im just wondering, is this the best way to go about it. Chuck every song in the same table? Link to comment https://forums.phpfreaks.com/topic/21514-mysql-table-structure/ Share on other sites More sharing options...
AndyB Posted September 21, 2006 Share Posted September 21, 2006 If that's the full extent of your design, then that's fine. If 'next week' you decide to have artist bio information you might want to modify the design now to two tables with the one you describe using an artist_id that points to a record in the artist_bio table where the artist's detailed information exists. Link to comment https://forums.phpfreaks.com/topic/21514-mysql-table-structure/#findComment-95986 Share on other sites More sharing options...
fenway Posted September 21, 2006 Share Posted September 21, 2006 Well, IMHO, songs have views and names, and nothing else -- you should pull out artist & genre into another table, and just link them with a FK. Link to comment https://forums.phpfreaks.com/topic/21514-mysql-table-structure/#findComment-96066 Share on other sites More sharing options...
ryan.od Posted September 24, 2006 Share Posted September 24, 2006 You should look into database normalization (search it) and break this table into multiple tables. Link to comment https://forums.phpfreaks.com/topic/21514-mysql-table-structure/#findComment-97752 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.