I have an issue that I'm trying to resolve with my first database i'm creating for a client. I'm creating a reservation system for a river tour company and in the database I'm having a problem figuring out an efficient table layout.
The business requirements:
1) Ability to take a persons information down (name, phone number, age)
I have solved this one by creating a
table that is identified by
.
2) Ability to sign a person up for various trips. (They offer a kayak trip, a tube trip, and a rafting trip)
3) Each trip will go out twice a day, everyday at set times (7:30AM and 12:30PM)
After having my person table set up, I'm not really sure where to go from there..I tried setting up a
table that has foreign keys from a
table, and
table, and the
table, but that didn't really make sense to me so I deleted those tables and am only left with my
table. Where should I go from here?
The business requirements:
1) Ability to take a persons information down (name, phone number, age)
I have solved this one by creating a
Code:
person
Code:
PersonID
2) Ability to sign a person up for various trips. (They offer a kayak trip, a tube trip, and a rafting trip)
3) Each trip will go out twice a day, everyday at set times (7:30AM and 12:30PM)
After having my person table set up, I'm not really sure where to go from there..I tried setting up a
Code:
TripSchedule
Code:
Date
Code:
Time
Code:
Person
Code:
Person