The Area being Modelled is :-
Skip Ordering
The Business Rules are :-
This database will be used for people ordering a skip for getting rid of rubbish etc.

Because there are 2 parts to the job (Drop the skip - then lift the skip when the days 
hire is up or when the customer rings to say its full) i will need to store:

Order details:
Cost
Customer details
Order date
Skip type


DropRequiredDate
DropAllocatedDate (date job is given to the driver) DropDriver DropConfirmedDate

LiftRequiredDate
LiftAllocatedDate (date job is given to the driver) LiftDriver LiftConfirmedDate

My question really is should this order part of the database consist of 3 tables :-
1 for order details, 1 for the drop details and 1 for the lift details 

or should i put this information all into 1 table?

If i go with creating the 3 tables
When the order is taken i know when the drop part is required so i would have to 
create an entry in the drop table i will also know the lift required date based 
on the days hire so i would also need to create an entry in the lifts table.

Is this overkill?


Barry says The Things of Interest
C.1 Customers
C.2 Orders
C.3 Skips




 © DataBase Answers Ltd. 2009