Ahh I ya actually the date is instead of weeks broken into days is a way better idea.
So I'd have a table that has an employee, the job he is at, a date, and the hours they worked that day.
Like this?
Employee | Job | date | hours
John Doe Job A 10-05-15 10
John Doe Job A 10-06-15 10
John Doe Job A 10-07-15 8.5
John Doe Job A 10-08-15 8
John Doe Job A 10-09-15 9
John Doe Job B 10-12-15 8.5
John Doe Job B 10-13-15 8
John Doe Job C 10-14-15 9
John Doe Job C 10-15-15 9
John Doe Job C 10-16-15 9
It seem a little weird to me to have so many rows being created with the same Employee and Job columns but I can't think of any other way to store them in a database. And I know my project isnt that big but for huge projects with a method similar to this it looks like it could be creating an insanely huge number of rows every day. Is mySQL extrememly fast at pulling out data from billiions or possibly even trillions of entries and is this the right way to tackle a problem like this?