| | |
Table Desgin
Please support our Database Design advertiser: PostgreSQL or MySQL? Compare and contrast the two most popular open source databases
![]() |
•
•
Join Date: Apr 2009
Posts: 1
Reputation:
Solved Threads: 0
I have a question about table design and normalization.
The table in questions is:
Is that table nomalized? or should i break it into two tables. One for all work orders and one for approved work orders that extends workorders and move all the info about approved work orders to the new table?
thanks
The table in questions is:
WorkOrder
WorkOrderID
Submitted by
dateSubmitted
DesiredcompletionDate
discription of task
schoolID
RoomNum
DateStarted
Datefinished
cost of materials
labor
overhead
completed by
completion comments
priorityid
budgetid
approved
approveddate
approved by
approvedcommentsIs that table nomalized? or should i break it into two tables. One for all work orders and one for approved work orders that extends workorders and move all the info about approved work orders to the new table?
thanks
Strictly speaking, the table appears to be normalized since the fields with similar content is not the exact same content. However, I do like Stylish's recommendation.
I would recommend using a 'status' table, which has fields similar to the following:
ID, Status ID, Date, Status Updated By, Comments
I would recommend using a 'status' table, which has fields similar to the following:
ID, Status ID, Date, Status Updated By, Comments
![]() |
Other Threads in the Database Design Forum
- Previous Thread: Loans payment ER
- Next Thread: College Assignment
| Thread Tools | Search this Thread |





