I am looking to develop an online accommodation
booking engine to complement my accommodation directory.
I am trying to get my mind around the structure of the database necessary to facilitate an online booking centre.
clearly I have a room type table and a rooms table with a rooms type column to match the id's in the room type table.
the issue that I have is trying to conceptualise the database format of the bookings register itself.
I was thinking along the line of having a bookings table consisting of id column;room type column; room number column; checkin date; checkout date. then when a user makes a booking indicating the room type and the check in and checkout date the bookings table is queried to count the number of records (bookings) that already exist for that room type and dates. As long as the number of matching records found is less than the number of rooms available of the specific room type then the booking can be made as availability exits. The logic may work fine within a hotel structure where the total number of rooms available in a hotel are constant then the above system may work
The problem exists when from one day or week to the next the total number of rooms available can change as is the case within a serviced apartments environment. Therefore I need to be able to record and change the total number of rooms available from one night to the next so that there is never any chance for over bookings
if anyone can assist and shed some light on a functional structure to meet the needs of both a serviced apartments environment (where the total available room nights available from one night to the next may alter) and hotel structure (where the total number of room nights available is contestant every night of the week) I would appreciate your perls of wisdom
I am trying to get my mind around the structure of the database necessary to facilitate an online booking centre.
clearly I have a room type table and a rooms table with a rooms type column to match the id's in the room type table.
the issue that I have is trying to conceptualise the database format of the bookings register itself.
I was thinking along the line of having a bookings table consisting of id column;room type column; room number column; checkin date; checkout date. then when a user makes a booking indicating the room type and the check in and checkout date the bookings table is queried to count the number of records (bookings) that already exist for that room type and dates. As long as the number of matching records found is less than the number of rooms available of the specific room type then the booking can be made as availability exits. The logic may work fine within a hotel structure where the total number of rooms available in a hotel are constant then the above system may work
The problem exists when from one day or week to the next the total number of rooms available can change as is the case within a serviced apartments environment. Therefore I need to be able to record and change the total number of rooms available from one night to the next so that there is never any chance for over bookings
if anyone can assist and shed some light on a functional structure to meet the needs of both a serviced apartments environment (where the total available room nights available from one night to the next may alter) and hotel structure (where the total number of room nights available is contestant every night of the week) I would appreciate your perls of wisdom
Kind Regards
Claude
Raiola (Director)
AustralianAccommodation.com Pty. Ltd.
Mobile: 0414 228
948
Fax: 07 3319 6444
Websites:
www.AustralianAccommodation.com
www.AccommodationNewZealand.com
www.HospitalityPurchasing.net
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
