Results 1 to 4 of 4

Thread: Design Dilemma

  1. #1
    Join Date
    Mar 2003
    Location
    Brampton, Ontario, Canada
    Posts
    27

    Design Dilemma

    Hello,
    I have what seems to be a complicated design dilemma regarding an
    events program that sells tickets to an event at various venues.

    I felt that the explanation of the problem would be better illustrated
    via a web page with some graphics showing the form and table design.
    This is NOT an advertisement.
    It is a genuine request for assistance.
    Please feel free to visit the page to understand my problem.
    Any and all advice will be sincerely appreciated.
    http://www.smartbizops.com/Tickets.htm

    Thanks in advance
    Brad

  2. #2
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171

    Re: Design Dilemma

    Originally posted by BradCO
    Hello,
    I have what seems to be a complicated design dilemma regarding an
    events program that sells tickets to an event at various venues.

    I felt that the explanation of the problem would be better illustrated
    via a web page with some graphics showing the form and table design.
    This is NOT an advertisement.
    It is a genuine request for assistance.
    Please feel free to visit the page to understand my problem.
    Any and all advice will be sincerely appreciated.
    http://www.smartbizops.com/Tickets.htm

    Thanks in advance
    Brad
    It seems to me that your problems derive from the fact that your design merges the concept of physical seats and the usage of those seats for a particular event. Although one talks about selling seats at an event, in reality they are just rented out for the night! That's why you see "duplication" in keeping records for more than a year.

    I think your model should be more like:

    VENUE --< SECTION --< SEAT (physical seat)

    EVENT --< ORDER --< SEAT ALLOCATION >-- SEAT

    So there is only one seat called L 501 in Clevelend, but it may be allocated many times (for different events).

  3. #3
    Join Date
    Apr 2003
    Location
    London, England
    Posts
    42

    Re: Design Dilemma

    >[QUOTE][SIZE=1]Originally posted by BradCO
    >Hello,
    >I have what seems to be a complicated design dilemma regarding an
    >events program that sells tickets to an event at various venues.

    Check out this page of my Database Answers web site which has seven different Events and Reservations Data Models which might help you :-
    http://www.databaseanswers.com/data_models/index.htm

    Barry
    Principal Consultant
    Database Answers

  4. #4
    Join Date
    Apr 2003
    Location
    Nanjing, China
    Posts
    5
    It's not a good idea to put irrelevant information into one table. For example, EventID and ClientID shouldn't be in table Venues.

    My suggestion:

    Venues(VenueID PK, Venue, ...);
    Sections(SectionID PK, VenueID FK, SectionName, ...);
    Seats(SeatID PK, SectionID FK, Row, ...);
    Events(EventID PK, Date, ...);
    Tickets(TicketID PK, SeatID FK, EventID FK, Status, ...);
    Clients(ClientID PK, Address, ...);
    Orders({TicketID FK, ClientID FK} PK, Price, ...);

    Hope this helpful.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •