Reservation System Database Design

I need some ideas on a mySQL database design for a reservation system,
much like a doctor's office (hopefully without the long wait).

My client has 12 work areas. She wants her clients to be able to sign up
for sessions at these areas on-line. The clients will sign up for either
1.5 or 2 hours, and she only wants 4 people to be able to start every
half hour.

I would like to avoid having to iterate through every half hour of every
day to determine if there are available opennings that the client could
sign up for.

My initial thought was to have a table of sessions, which had a field
for start time and end time, then use a COUNT query to find out how many
users had a start time at that half hour, but we need to present the
user with a view of which time slots are available for each half hour.
Since the interface is via the internet, I am afraid that this will
require a lot of data to be sent back and forth.

If anyone has any suggestions on an efficient way to do this, I would
really appreciate some assistance.

Thanks in advance.

Gary Holt

"Gary" wrote in message

> I need some ideas on a mySQL database design for a reservation system,
> much like a doctor's office (hopefully without the long wait).
>
> My client has 12 work areas. She wants her clients to be able to sign up
> for sessions at these areas on-line. The clients will sign up for either
> 1.5 or 2 hours, and she only wants 4 people to be able to start every
> half hour.
>
> I would like to avoid having to iterate through every half hour of every
> day to determine if there are available opennings that the client could
> sign up for.
>
> My initial thought was to have a table of sessions, which had a field
> for start time and end time, then use a COUNT query to find out how many
> users had a start time at that half hour, but we need to present the
> user with a view of which time slots are available for each half hour.
> Since the interface is via the internet, I am afraid that this will
> require a lot of data to be sent back and forth.
>
> If anyone has any suggestions on an efficient way to do this, I would
> really appreciate some assistance.
>
> Thanks in advance.
>
> Gary Holt

If it is a reservation system for a Dr.'s office then make sure you read the
HIPAA regulations. (if you are in the US) You probably don't look good in
a florescent orange jump suit.
Jim