Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am creating a database to track occurrences of incidents on buses based on an existing system. Currently the drivers can set a default bus number, which is used to pre-populate the bus number on the incident form. Where they can change that then, if they are driving another bus. This is a selection made by the driver. Not a bus assigned to them, per say. I was going to put this field in the staff table, not the bus table. However, someone said I should not, that I should put it in the bus table. I guess it would technically work either way, but I don't feel like the field belongs to the bus - it belongs to the staff member. Am I overthinking this?

share|improve this question
2  
No, you are right. It's a selection made by a driver. So it belongs to the stuff table or a new table with 1-1 relationship with the stuff table. It couldn't on the bus table as a bus could be selected (I guess) as default by more than one drivers. –  ypercube Jul 1 '13 at 18:26
    
Thank you! Since you said it that way, that made me think I may have misunderstood them. Perhaps they were recommending a supporting table, rather than further "cluttering" the main table. I'll consider that more. I was just second-guessing myself. Thanks again! –  user2539901 Jul 1 '13 at 20:11
1  
As an aside, if it is an attribute of the driver entity (which it sounds like it is) then adding it to the driver table is not "cluttering". –  Greenstone Walker Jul 1 '13 at 20:48

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.