Database Design

Gavx

Registered User.
Local time
Tomorrow, 07:27
Joined
Mar 8, 2014
Messages
155
I am designing my first database for a travel agent that sells products such as bus tickets, accommodation, ski lift tickets etc.

I started putting all of these items into a Product table. I have now realised these products have some differences. For example a bus ticket is only good for a day. Accommodation has different classes of rooms and a date in and date out. Ski lift tickets also come in different classes - adult, child, duration.

Should I group the all product items in one table along with the characteristics which are common, for example price, cost and supplier ID and then put the characteristics which are not common in seperate tables. Say an AccomodationRef table that contains product sold ID, RoomClass, DateIn, DateOut?

thanks
 
As a general answer i suggest you google "normalization" and read up. That should point you in the right direction.
 

Users who are viewing this thread

Back
Top Bottom