Unfortunately we're using 1.5 so "NOW" isn't available to us. 

 We're running the statements in real-time so a 30 minute difference is 
definitely wrong.. It is also exactly 30 minutes which leads me to believe 
there's some kind of funny offset due to timezone or something to that effect 
that we aren't seeing for whatever reason. I thought if I figured out where the 
"CURRENT_TIMESTAMP" statement is pulling its time from I would know where to 
look for the issue.
 

Reply via email to