Re: Basic Design Question

[Vsevolod Afanassiev]

It depends on the business logic:
- If you need to track all attendees for an event then EVENTS would be parent table and ATTENDEES would be child table. For example, if I was organizing Oracle Open World conference the EVENTS table wold have only a few records: OOW2010, OOW2011, OOW2012, etc while there will be thousands of attendees.
- If you need to track all events attended by a person then ATTENDEES would be parent table and EVENTS would be child table. For example, if I decided to keep track of events attended by my family members then attendees would have only a few lines (me, my wife, our kids) while table EVENTS would contain movies, sleepovers, etc.