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.
[firebird-support] Re: Firebird 1.5 - CURRENT_TIMESTAMP difference
[email protected] [firebird-support] Sun, 14 Dec 2014 14:14:39 -0800
- ... [email protected] [firebird-support]
- ... Svein Erling Tysvær [email protected] [firebird-support]
- ... Tim Ward [email protected] [firebird-support]
- ... Nick Upson [email protected] [firebird-support]
- ... Mark Rotteveel [email protected] [firebird-support]
- ... Tim Ward [email protected] [firebird-support]
- ... Mark Rotteveel [email protected] [firebird-support]
- ... Tim Ward [email protected] [firebird-support]
- ... [email protected] [firebird-support]
- ... 'Leyne, Sean' [email protected] [firebird-support]
- ... Helen Borrie [email protected] [firebird-support]
- ... Mark Rotteveel [email protected] [firebird-support]
- ... 'Bogdan' [email protected] [firebird-support]
