Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What would be the best database design for employee clocking and out? Right now I have two tables.
Employee Base Table: Employee Id, relevant information like name and address, clocked in column
Employee Clocked in Table: Employee id, clock in date, Clock in Time, Clocked Out Time.
Is this a good way to track clocked in and clocked out? I appreciate any help
1) I assume “clocked in column” in employee table is for dynamically tracking whether an employee is clocked in? If so, I’d recommend a separate “clocked in” table instead – you would usually prefer employee table to be stabler.
2) Your schema does not specify if EID and date are unique in second table. Doing so would prevent people from clocking out mid-day, so take that under consideration when building indexes