Results 1 to 3 of 3

Thread: Structure

  1. #1
    Join Date
    Apr 2012
    Posts
    5

    Structure

    I am building a theatre booking system and was considering the following structure:

    BookingTable
    BookingID(PK)
    CustomerID(FK)
    ShowID(FK)
    VenueID(FK)
    SeatID(FK)
    ShowDate
    ShowTime

    VenueTable
    VenueID(PK)
    Name
    Address
    Phone
    Fax



    ShowTable

    ShowID(PK)
    GenreID(FK)
    DirectorID(FK)
    Title
    Price
    ShowArtUrl
    Synopsis

    Customert
    CustomerID(PK)
    Name
    Address


    Is this structure ok?

  2. #2
    Join Date
    Nov 2004
    Location
    out on a limb
    Posts
    13,692
    how do you know what seats are booked or availabel for a specific show
    how do you constrain or validate that a booking is for a specific show and is in a unique seat position (assuming you are selling tickets for seating as opposed to say a free for all or standing room only)

    how do you know what seats are available in the venue

    how do you know what performances are being put on in which venues

    how many tables do you need for this assignment
    I'd rather be riding on the Tiger 800 or the Norton

  3. #3
    Join Date
    Apr 2012
    Posts
    5
    My apologies I forgot to include a seat table:

    Seat Table
    SeatID(PK)
    BookingID(FK)
    CustomerID(FK)

    and was going to use a constraint class against this table to set the amount of seats?
    Regarding the number of tables there is no requirement or limit, personally I would like to go with the most simplistic design as possible
    Last edited by Campbells; 04-24-12 at 05:01.

Posting Permissions

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