Sent: Monday, December 15, 2014 8:50 AM To: [email protected] Subject: Re: [firebird-support] Re: Firebird 1.5 - CURRENT_TIMESTAMP difference
On 14 Dec 2014 14:14:21 -0800, "[email protected] [firebird-support] <mailto:[email protected]%20[firebird-support]> " <[email protected]> wrote: > 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. Do you also get this 30 minute difference if you execute SELECT CURRENT_TIMESTAMP FROM RDB$DATABASE from ISQL and/or Flamerobin, or only inside your application? What is your own timezone, and what is the server timezone? Mark The last time i've seen such behaviour, we found there was another job scheduled every 30 minutes that took all the resources Regards Bogdan --- avast! Antivirusna zaščita. E-pošta je čista. Ne vsebuje virusov in zlonamerne programske kode. Prenesite si avast! Antivirusno zaščito iz www.avast.si. http://www.avast.com
