DB Structure

[Xtremer360]

Okay so say I have a table for scheduled wrestling events that looks like this:

 

ID : (auto- increment, primary key)

eventNameID:  (ID of the event name from the eventNames table)

label: (label of the event will either be the next incrementing number from the previous occurance of event or the year in which its happening)

bookingDate: (date of which the event is taking place)

numMatches: (number of matches set for the event)

numSegments: (number of segments set for the event) (a segment might be like a backstage interview for example)

arenaID: (ID of the area from the arenas table)

eventStatusID: (ID of the event status  from the eventStatuses table)

 

 

The next step after creating the event is setting up the matches and segments. My form is setup for an area for the show introduction, and for each of the matches for the event it has the following:

match type:  singles, tag team, etc. 

title: any of the title belts that could be on the line (can have more than one attached)

stipulation: any of the stipulations that could added to the match (can have more than one attached)

competitors: a list of characters that are competting for the match (will have more than one attached)

match writer: ID of the person responsible for writing the match

match title: the title for the match NOT the title belt but the title

preview: a preview for hyping up the match

 

And for each of the segments is the following:

 

segment Writer: ID of the user responsible for writing the segment

segment After: a dropdown that represents the Introduction, and each match which dynamically field because of it telling how many matches there are in the event

 

I'm trying to come up wth as many ideas as the BEST way to store all this information.