Jump to content

MYSQL Table Structure


jaymc

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

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

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.