|
music files and mysql database design
Hey everyone,
I'm new to this site, so sorry for any n00b mistakes. I'm building a website for rock music where each rock band will be represented by an id, each album will be represented by an id, and each song represented by an id (all of these will be in a mysql v5 database). Users will be able to register for the site and add bands, songs, and albums and maybe music files (although originally I will be the only one uploading music files to the site--making sure i have each band's consent). I'm planning on having each unique song have data in the database independent of whether a music file exists on the site for that song (each version of a song will have a unique id -- different id for demos, final masters, live recordings, acoustic recordings, remasters, remixes, and other edits). The music will mostly be used just for streaming to the users. I have thought up this as a way to handle the music files:
just have a folder called songs/ on the site where i have the individual mp3 files each named with the id of the song in the database. for example, if song "Killing It" has id 345, i would name the file 345.mp3.
My question is: is this a good way to do things? What are the advantages and disadvantages of doing things this way? Can you suggest any better ways of handling the mp3 files?
Thanks guys!
Last edited by soulkarver; July 12th, 2008 at 06:37 PM..
|