SQL music playlist database design
How about something like this?
Songs:
id title length artist_idArtists:
id namePlaylists:
id title user_id Playlists_Songs:
playlist_id song_idUsers:
id name email
In terms of relational design, you need two tables for playlists, one holding the playlistname (key, playlistname), one for the actual playlists (key,playlistkey,trackid)Table for tracks holding mp3 tag details (key, track title, artist key, album .... Etc)Table for Artists (key, name, band). You can break it down further applying the principle that you should not duplicate data for instance holding a playlistname in more than one table. By creating views, you knit all this together
However, if you are using android, this database already exists.