Booking system dates in database_问答_开发者_运维开发者技术经验分享

I need some help with the following:

I am setting up a booking syst开发者_StackOverflow社区em (kind of hotel booking) and I have inserted a check in date and a check out date into database, how do I go to check if a room is already booked?

I have no clue how to manage the already booked days in the database. Is there anyone who can give me a clue how this works? And maybe where I can find more information?

Well, I didn't understand very well your question, but my suggestion is to you to add a state field, in which you can control the current state of the "booked" item. something like

Available
Under Maintenance
Occupied

Or whatever bunch of states that work for you.

[EDIT] The analysis that I use to do for that case is as follows: Take for instance, your room is currently booked with these date range:

Init Date: Feb 8
End Date: Feb 14

Success Booking Examples

Init Date: Feb 2
End Date: Feb 6
Init Date: Feb 15
End Date: Feb 24

You should check that the booking attempt satisfies these conditions:

Neither "Booking Init Date" nor "Booking End Date" can be inside of the already booked date.

Example:

Init Date: Feb 2
End Date: Feb 10 (Inside the current range (Feb 8 to 14))
Init Date: Feb 12 (Inside the current range (Feb 8 to 14))
End Date: Feb 27
1. if "Booking Init Date" is less than current init date, "Booking End Date" should also be less than current init date
Init Date: Feb 2.
End Date: Feb 27 (Init date before, but end date later)

This is an interesting question - not least because I don't believe that there is a single ideal answer as it will depend to some extent on the nature of the "Hotel" and the way in which people are placed in rooms and to a further extent on the scale of the question.

At the most basic level you have two ways that you can track occupancy of rooms:

You can have a table with one row per room per day that defines the state of that room on that date (and possibly the related booking if occupied)
For each room you maintain a list of "bookings" (which as already suggested will have to include states for when a room is unavailable for maintenance).

The reason that its an interesting question is that these both immediately present you with certain challenges when maintaining the data and searching for occupancy in the case of the former you're holding a lot of data that may not be needed and in the case of the latter finding gaps in the occupancy for new bookings is perhaps more interesting.

You then (in both cases) have a futher problem of resource allocation - if your bookings tend to be for two days and you system results in 1 day gaps between bookings you're going to need to re-arrange the occupancy to optimise usage... but then you have to be careful with bookings that need to be explicitly tied to specific rooms.

Ideally you would defer assigning a booking to a room for as long as possible (which is why it depends on the hotel - fine for 400 modular rooms rather less so for a dozen unique ones) - so long as there are sufficient rooms of the necessary standard available (which you invert, so long as there are fewer rooms booked than real rooms) during a target period you can take the booking. Of course you've still then got to represent the state of the rooms so this is in addition to the data you've got to manage.

All of which is what makes it interesting - there is considerable depth to the problem, you need to have a fairly decent understanding of the specific problem to produce an appropriate solution.

I have come to the booking problem from the perspective of avoiding a highly populated table, giving that the inventory is thousands rather than hundreds.

solution one - intervals

solution two - populate slots only when are occupied using the smallest unit (1 day)

solution three - generate slots in advance for each resource and manage the status

Solution one has smallest size footprint but since you cannot guess if your searched range is already in an interval or not - you have to read and compare the whole table.

Solution two solves this problem and you can search for a specific time-frame only but the table contains more lines. However since the empty slots are not written anywhere a high vacancy will reduce the size of the table. Another advantage is that old bookings can be transferred to a separate table.

Solution three increases the size of the table to a maximum minSlotresourcetime and the lines are generated in advance. The only advantage that I can think of is the cost of finding empty slots with a simple select. However generating the slots in advance looks like a terrible idea to me.