-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
mclient starts off with setting the time zone. Then subsequent time stamps are translated to that time zone before being sent to the client. The first query mclient sends is:
SET TIME ZONE INTERVAL '+01:00' HOURS TO MINUTE
(if your current time zone happens to be wintertime in Amsterdam).
On 29/10/15 13:29, Robin Cijvat wrote:
Hi all,
I am currently extending the NodeJS connector for MonetDB, that communicates with the mserver process using Mapi. However, I face some unexpected behavior when I insert timestamptz values into a table and then retrieve it. This is the Mapi:
TX: sCREATE TABLE bar (a timestamptz); RX: &3
TX: sINSERT INTO bar VALUES ('2015-10-29 11:31:35.000000+01:00'); RX: &2 1 -1
TX: sSELECT * FROM bar; RX: &1 0 1 1 1 % sys.bar # table_name % a # name % timestamptz # type % 32 # length [ 2015-10-29 10:31:35.000000+00:00 ]
As you can see, inserting the timestamptz string '2015-10-29 11:31:35.000000+01:00', results in it being stored as its equivalent '2015-10-29 10:31:35.000000+00:00'. If I do the same with mclient, this does not happen, and I get the exact same string back. Does anyone know why this might be happening? _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
- -- Sjoerd Mullender