[thelist] Database - advantage of mulitple tables?
r937
rudy at r937.com
Mon Aug 17 13:23:32 CDT 2009
there is not very much to be gained by splitting your current employee table
up, and plenty to be lost, primarily lost time and effort to ensure that
current apps continue to work against the redesigned database... and for
what?
are there any non-employees in the table? (you'd be surprised, i've seen
several examples of employee tables where the meeting rooms and cafeteria
are included, because the little app that produces the company phone
directory needed to include those phone numbers)
i wouldn't stick the training columns in there, though -- i'd use a new
table for that, and simply use the UserIDs from the employee table to track
the employees
rudy
http://r937.com/
More information about the thelist
mailing list