From: Jan Steinman Date: February 20 2012 5:22pm Subject: Re: Design advice for hotel availability program List-Archive: http://lists.mysql.com/mysql/226820 Message-Id: <513BF80F-4F96-424A-9E45-14C53C1DD7BC@Bytesmiths.com> MIME-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Where are your domain experts? You *are* consulting with them, no? If you don't know the answers, and don't have access to domain experts = to help you, I would design for the most general case, and factor out = exceptions as they prove to be so. "Pre-optimization" for exceptions = almost always turns out to be a bad choice. > From: Tompkins Neil >=20 > .... Am > I best using the following pattern >=20 > (1) Default rates/rooms stored in a generic table > (2) Any exceptions/changes/closed days to the daily rates are store in > a separate table. > (3) Any special offer exceptions are stored as a rule >=20 > All, should I consider that for any hotel, for any room, for any day I = have > a record in a huge single table ??? ---------------- Everything we think we know about the world is a model... None of these = is or ever will be the real world. -- Donella H. Meadows :::: Jan Steinman, EcoReality Co-op ::::