Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
This data is for a holiday cottage’s simple accommodation calendars.
The data is simple and stores dates when each cottage is booked.
The cols would be cottage_id, booked_from_date, booked_until_date and I would expect around 60 rows per user per year * 200-300 users.
I should put this is one table right?
COTTAGE
cottage_id,
address?,
other info…
USER
user_id,
name,
other info…
COTTAGE_RESERVATION
cottage_id,
user_id,
from_date,
to_date