Is there a "Best Practice" for this mySQL table structure question?
I have a table which will hold music events held in a city. Each musical event is a row in the Events table. One of the items to associate with each event is the people that will be attending, so that when we view an event we can see:
People attending this event: [list of people names and details from table PEOPLE]
My question is: should the Events table have multiple rows per event for each person that will be attending, e.g.
should the Events table have one row per event with a column for persons attending but store this value as a comma separated value, e.g.
is there a best practice around how I should be structuring such a table?
Also, assume that each person will only ever attend one event. Should the PERSONS table also have a column for Event ID linking each person to an event? I find this to be unnecessary since the Events table will have a column for persons attending, but not sure if it's prudent to add an event ID to the persons table from the get-go.
Help would be appreciated.