Stadium Representation in a Database
How would I represent a stadium object in a database?
I'm designing a ticketing application to sell tickets to events. These events take place in stadiums. A stadium has stands, stands have tiers, tiers have sections and sections have seats.
But how do I represent all that in a database? Or should the ticket have all those properties associated with it? i.e. a ticket is for a seat in a section in a tier in a stand in a stadium?
Just some pointers on which way I should go with this please?
Last edited by jb007irl; May 27, 2004 at
In really, really simple terms you would:
stadium_id -- so that this stand is in a particular stadium
stand_id -- so this tier is in a particular stand
and so on...
So for any seat you could drill up to its section -> tier -> stand -> stadium.
And you see how many seat/tickets are sold in a stadium by linking the other way.
You might want to add an event table which might have a specific date because then you could sell many tickets for one seat (just on different dates).
Hope this helps
Thank you, what you've outlined here is basically the way I've set it up but I just wanted to make sure somebody else would do it in a similar way as I'm far from the best database designer in the world.
Thank you for replying.