Hi Ilya,
thanks a lot for the reply,
it is surprising that EPOCH is not always the same regardless of the
timezone.
I did a test on two Ignite instances, one on a host with timezone 'Europe /
Zagreb' and the other on UTC.
The EPOCH obtained in bash is the same on both hosts and the EPOCH obtained
in Ignite sql is not the same.
When I select CURRENT_TIMESTAMP() Ignite does not return timezone
information, how do distinct if returned timestamp is local time or UTC?
0: jdbc:ignite:thin://192.168.50.95/> SELECT CURRENT_TIMESTAMP(),
FORMATDATETIME( CURRENT_TIMESTAMP(), 'yyyy-MM-dd HH:mm:ss z', 'en',
'Europe/Zagreb');
+--------------------------------+--------------------------------------------------------------------------------+
| CURRENT_TIMESTAMP() | FORMATDATETIME(CURRENT_TIMESTAMP(),
'yyyy-MM-dd HH:mm:ss z', 'en', 'Europe/Zag |
+--------------------------------+--------------------------------------------------------------------------------+
| 2020-04-26 13:49:36.413 | 2020-04-26 13:49:36 CEST
|
+--------------------------------+--------------------------------------------------------------------------------+
1 row selected (0.002 seconds)
<http://apache-ignite-users.70518.x6.nabble.com/file/t2557/epoch_Ignite.png>
Best regards
Dren
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
