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.
Is it a good practice to have timestamps for the last row update in every table?
Or should they only be set where really needed?
How do I know where I will need an update timestamp later?
For which kind of information do they make sense?
row timestamps are used for row versioning in situations where you have optimistic record locking; i.e. 2 users editing the same record at the same time.
You can detect if the DB version has changed, by examining the current row timestamp with the timestamp found when you retrieved the row from the DB.