| Author |
Message
|
| marko.pitkanen |
 Posted: Thu Jan 07, 2016 7:37 am Post subject: IIB 9 timestamp problem - solved |
 |
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
We noticed for few days(27.12.2015 - 1.1.2016) weird behavior of following code
| Code: |
| CAST(CURRENT_GMTTIMESTAMP AS CHARACTER FORMAT 'YYYYMMddHHmmssSSS') |
It produced for example value 20161231225214889
Server is located in Finland.
Do you make up any explanations for the behavior?
Last edited by marko.pitkanen on Fri Jan 08, 2016 12:36 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jan 07, 2016 8:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
what's weird about the result?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| adubya |
| Posted: Thu Jan 07, 2016 8:05 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011
Posts: 377
Location: GU12, UK
|
| If the system clock is correct then returning a date of 31st December 2016 as the GMT representation would seem wrong. |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Thu Jan 07, 2016 8:51 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
| mqjeff wrote: |
| what's weird about the result? |
Date & Time corresponds to the event, but seems that the year was converted too early to 2016 and so event was stored to the far future.
--
Marko |
|
| Back to top |
|
|
| maurito |
| Posted: Thu Jan 07, 2016 11:09 pm Post subject: |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Fri Jan 08, 2016 12:32 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
|
| Back to top |
|
|
|
|
