Jump to content

Archived

This topic is now archived and is closed to further replies.

jaymc

MYSQL Table Structure

Recommended Posts

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 table

The query will be pretty straiight forward when someone wants to listen to a song, it will be selected by ID which will be unique

Anyway, Im just wondering, is this the best way to go about it. Chuck every song in the same table?

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
You should look into database normalization (search it) and break this table into multiple tables.

Share this post


Link to post
Share on other sites

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.