I am new to working with tables. I do understand the basics , I just cannot come with the ideal structure of the tables in the project I am working on.
It is a database for a shopping cart for golf holidays where clients can book a car, ask for several availabality requests for property rentals and book several Tee times.
My thoughts are to set up 4 tables. one for client details, one for car rental, one for property and one for tee times.
What I cannot come up with is an efficient structure for those cases where people do more than 1 availability request for property or booked more than 1 tee time on golf courses.
Is it the best structure to apply an unique ordernr to each submission and put each individual, for example, tee time booking on a new entry in the table with the unique ordernr as the Key or is there a better way?
thanks,
Ron
It is a database for a shopping cart for golf holidays where clients can book a car, ask for several availabality requests for property rentals and book several Tee times.
My thoughts are to set up 4 tables. one for client details, one for car rental, one for property and one for tee times.
What I cannot come up with is an efficient structure for those cases where people do more than 1 availability request for property or booked more than 1 tee time on golf courses.
Is it the best structure to apply an unique ordernr to each submission and put each individual, for example, tee time booking on a new entry in the table with the unique ordernr as the Key or is there a better way?
thanks,
Ron