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.
I am using a sysdate query in code to obtain the last updated rows in the past 3 hours (should be configurable). The database runs in GMT timezone and the application runs in PST timezone. The query looks like this
select * from <table> where updated_Date < sysdate - numdtodsinterval(3,'hour')
What is the recommended/best practice to firing such queries from application which has different timezones from the db.
I would have to say that the best practice for an application that covers a lot of timezones is to stop using the DATE datatype and start using the TIMESTAMP with TIMEZONE datatype.
I’m not saying that’s easy, just sayin’ that’s probably a best practice for a couple of reasons.
The main is that it eliminates any and all ambiguity. If you use DATE, no one can tell what that value was calculated based on. You know. Maybe you have a comment on the column (ideal) but maybe overlooked. If it’s a TIMESTAMP with TIMEZONE datatype, you’ve nailed a specific moment in time independent of my local clock.
But this assumes that you can change the database schema, which you probably can’t. So this serves as a warning for your next date column.