Posted by frizzle on 06/25/06 12:59

Geoff Berrow wrote:
> Message-ID: <BbWdnUHqd747YgDZnZ2dnUVZ_vydnZ2d@comcast.com> from Jerry
> Stuckle contained the following:
>
> >
> >I'd suggest you read up on "database normalization" and how it prevents the
> >problems which can be caused by your method.
>
> Indeed, and the OP should make sure that this is correct before doing
> any coding.
>
> As a lecturer I've seen students tackle this many times. You solo
> artists, have bands with members, artists who perform as solo artists
> and part of bands, albums and tracks, compilation albums, singles, DVDs
> and concert performances. Quite a lot to consider. A properly thought
> out entity relationship diagram will save a lot of grief later on.
>
> --
> Geoff Berrow (put thecat out to email)
> It's only Usenet, no one dies.
> My opinions, not the committee's, mine.
> Simple RFDs http://www.ckdog.co.uk/rfdmaker/

Well, i'wanted to keep the information as little as possble, but i
think i kept it too little.

What it comes to bands with multiple artists, who'd might go single,
swap labels and style, i've thought about this, but the site should be
quite simple (for now).

a rough sketch:

Artists / bands -> have multiple songs, have multiple genres
Songs -> have a single artist*, have multiple emotions/moods
Genres -> have multiple artists
Emotions/moods -> have multiple songs

*songs with collaborations etc could be added as a new artist.

The tables roughly look like this:
Artists -> info about artist etc.
Genres -> small info with genre
Combo_ar_ge -> combination table, uses artists id, and genre's id to
combine
Songs -> little info about the song, linked to artist by artist id
Moods -> small info about some emotions/mood
Combo_so_mo -> combination table, uses songs id, and mood's id to
combine


So the data structure isn't as deep as it could/should be. I'm trying
to build it focussed on user-friendly-ness (?)
Artists/bands can be added in a flash, without structuring any bands
first, so you'd have to be sure all individual band members are in the
database first. The same goes for songs, i've also thought about albums
with various artists, artist feat.artist etc., but i think the user
would have to enter so much info it would force them to take more time.
And that would make, i believe, the website too unfriendly and would
raise the effort it takes to simply add a song. (i do want to build
such an application in the (near) future though)

The first reaction to this topic would'nt work in this case AFAIK
because the amount of Genres is dynamic. Why i built it many to many,
is because i wanted to make sure that near-infinite genres could be
added to an artist/band. Also AFAIk i know this doesn't go against any
normilazation standards ...

Frizzle.

[Back to original message]