Re: best design for seating reservation type database

From: --CELKO-- <71062.1056_at_compuserve.com>
Date: 13 Oct 2002 11:13:00 -0700
Message-ID: <c0d87ec0.0210131012.59c85423_at_posting.google.com>


>> Should you have a table with 200 rows, one for each row from the
very start? Or should you start with no rows, and assume that if a row is not present, that seat has no data yet <<

I'd start with all the seats and have a status code. You know it exists already and you know its status; record that fact. Some of the status codes ill also include things like "out for repairs" that make a seat un-reservable and non-transferable. If you add 20 more seats, your application code would have to change to allow you to sell them, since you have not recorded the theatre size in the database. You cannot do these things in your model because it leaves out facts. Received on Sun Oct 13 2002 - 20:13:00 CEST

Original text of this message