From: Neil Tompkins
Date: February 20 2012 10:22pm
Subject: Re: Design advice for hotel availability program
List-Archive: http://lists.mysql.com/mysql/226824
Message-Id: <110F58BB-F009-471D-8F94-DAED8555082F@googlemail.com>
MIME-Version: 1.0 (1.0)
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi

I am trying to get some background information with regards the design.  I h=
ave a fair idea but would like advice from anyone that has previously worked=
 on similar projects.=20



On 20 Feb 2012, at 17:22, Jan Steinman <Jan@stripped> wrote:

> Where are your domain experts? You *are* consulting with them, no?
>=20
> If you don't know the answers, and don't have access to domain experts to h=
elp 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 tur=
ns out to be a bad choice.
>=20
>> From: Tompkins Neil <neil.tompkins@stripped>
>>=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 ha=
ve
>> a record in a huge single table ???
>=20
> ----------------
> 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 ::::
>=20
>=20
>=20
>=20
>=20
> --=20
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql
>=20