This article describes a proposed DB design for a “Reservation System”.
Summary
There are no complicated functions.
All you have to do is decide on a range of dates and times and make a reservation.There is no user registration.
Think of it as a basic form of reservation system.
The use case is likely to be in a place where an individual is providing a service for a set amount of time.
If this is all there is to it, it is really basic, as it would be better to use Google Calendar, etc. to handle this.
Design Details
ERD
erDiagram
RESERVATIONS {
int id PK
datetime reservation_start_datetime
datetime reservation_end_datetime
string customer_name
string customer_email
datetime created_at
datetime updated_at
}
Tables
reservations
| 物理名 | 論理名 | 型 | Null | 備考 |
|---|---|---|---|---|
| id | ID | int | primary | |
| reservation_start_datetime | Start of reservation date time | datetime | ||
| reservation_end_datetime | End of reservation date time | datetime | ||
| customer_name | Customer name | varchar(255) | ||
| customer_email | Customer email | varchar(255) | ||
| created_at | Record creation date time | datetime | ||
| updated_at | Record update date time | datetime |
