I am trying to get some background information with regards the design. I have a fair
idea but would like advice from anyone that has previously worked on similar projects.
On 20 Feb 2012, at 17:22, Jan Steinman <Jan@stripped> wrote:
> 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 <neil.tompkins@stripped>
>> .... Am
>> I best using the following pattern
>> (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
>> 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 ::::
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql