Re: Design advice for hotel availability program
Verify the regulation that a Hotel should submit, read the part of the occupation reports, information gathering, ask management for their currents report... Remember the data output should came from the data stored... On Mon, Feb 20, 2012 at 4:42 PM, Chaim Rieger li...@up-south.com wrote: On 2/17/2012 4:01 AM, Tompkins Neil wrote: Hi, I'm in the process of starting to design a hotel booking system that will eventually consist of over 10,000 hotels all with different room types, rates and availability for different dates. My question is does anyone have any experience with regards the best way to store the daily rates. 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 ??? Thanks for any help and input. There is already more than one package out there that does what you are trying to do, so why not take a look at how they do the db stuff. also keep in mind that you are working two reservations at once for each entry a guest requests an asett (the room) a guest then promises to pay a certain amount for an asset an asset can be tied to a variety or prices, but only one at a time, unless certain conditions are met. so no its not easy to do, but it has been done. http://drupal.org/project/uc_**hotel http://drupal.org/project/uc_hotel (ps. no i do not do drupal) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Design advice for hotel availability program
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.tompk...@googlemail.com 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
Re: Design advice for hotel availability program
Hi,
Nobody answers because this is a very wide question about software
engineering,
Trust me, It seems like a simple question but it is not.
The only advice I can give you is to try to imagine all possible
scenarios/use-cases before starting the design.
Cheers
Claudio
2012/2/20 Jan Steinman j...@bytesmiths.com
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.tompk...@googlemail.com
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
--
Claudio
Re: Design advice for hotel availability program
Hi 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 j...@bytesmiths.com 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.tompk...@googlemail.com 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 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Design advice for hotel availability program
On 2/17/2012 4:01 AM, Tompkins Neil wrote: Hi, I'm in the process of starting to design a hotel booking system that will eventually consist of over 10,000 hotels all with different room types, rates and availability for different dates. My question is does anyone have any experience with regards the best way to store the daily rates. 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 ??? Thanks for any help and input. There is already more than one package out there that does what you are trying to do, so why not take a look at how they do the db stuff. also keep in mind that you are working two reservations at once for each entry a guest requests an asett (the room) a guest then promises to pay a certain amount for an asset an asset can be tied to a variety or prices, but only one at a time, unless certain conditions are met. so no its not easy to do, but it has been done. http://drupal.org/project/uc_hotel (ps. no i do not do drupal) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Design advice for hotel availability program
Hi, I'm in the process of starting to design a hotel booking system that will eventually consist of over 10,000 hotels all with different room types, rates and availability for different dates. My question is does anyone have any experience with regards the best way to store the daily rates. 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 ??? Thanks for any help and input. Best, Neil
