query for attendance table in mysql

Question

0.00/5 (No votes)

See more:

I m doing project on attendance management systm..the problem is that in this project..how i insert the arrival or departure time in same row in two different times..
what should be the query for this..??

Posted 28-Oct-13 0:09am

Member 10364673

Add a Solution

Comments

Shubham Choudhary 28-Oct-13 6:17am

hi!! by logic its not a good idea if u insert record in same row its not possible you want to update this row and when u update row so first inserted record in deleted
so you have to do insert detail by date and time and when you want to see report . customize report according to u

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

W∴ Balboos, *GHB* · Answer 1 · 2013-10-28T01:54:00

I have found that a better way to handle this type of scenario is to have only a single record for in and and a single record for out. The table would be very simple: WHO, WHEN, WHAT.

WHAT is simply a way of marking punch-in and punch-out. You can use true/false, I/O, or whatever. This is because someone may forget to punch in or out, and thus, you can tell when you retreive the data. If you assume perfection, you could leave this out . . . but I wouldn't.

Retrieve Data: Now, all you need to do is get all data for a single WHO, in order of WHEN.

Why this way? Because you don't have to spend the time (mentally or computationally) deciding how to retreive an existing entry. Chronology takes care of that for you.