title: Structure of a music database - multiple or single table?
body: <p>I'm creating a music player, where the user can search for artists, albums, or songs. </p>
  
  <p>I have created a script that reads all the tags from the mp3s in the music library, and updates a database of songs, in a single table, containing artist names, albums, track titles, etc.
  Currently, this works well, because it can scan for any changes in the music library, and add/delete rows for corresponding songs in the database.
  This scan routine is therefore a fairly short an easy to understand piece of code, because it maintains only a single table.</p>
  
  <p>I understand the database would be more powerful if artists, albums, and tracks have their own table, and are all linked to each other. I haven't done anything about the search part yet -- how screwed am I, if I keep everything in one table?</p>
  
  <p>Thanks.</p>