J
jmDesktop
Hi, I am designing a table that has an employee and the days of the
week they work. Since there is one and only schedule that every
employee will ever have, is there any reason to not have a table that
has:
employee:
employeeid
employeename
sunstart
sunend
monstart
tuestart...and so on
wed..
thur..
frid..
sat..
I admit this is hideous, but I can't think of a reason to have a
second table for the actual schedule. Or is this better, worse,
neither:
employee table:
empid
....
schedule table:
schedid
empid
Day //like 1-7
DayStart //datetime field with work start time
DayEnd //datetime field with work end time for that day
Is either of these correct? Thanks.
week they work. Since there is one and only schedule that every
employee will ever have, is there any reason to not have a table that
has:
employee:
employeeid
employeename
sunstart
sunend
monstart
tuestart...and so on
wed..
thur..
frid..
sat..
I admit this is hideous, but I can't think of a reason to have a
second table for the actual schedule. Or is this better, worse,
neither:
employee table:
empid
....
schedule table:
schedid
empid
Day //like 1-7
DayStart //datetime field with work start time
DayEnd //datetime field with work end time for that day
Is either of these correct? Thanks.