From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
---|---|
To: | Edson Richter <edsonrichter(at)hotmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Driver behaves differently with prepareThreshold and timestamp fields when daylights is active (was Re: Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102) |
Date: | 2016-01-11 22:31:37 |
Message-ID: | CAB=Je-GLAWr99jb6F3KmGksNm-F0V5eX2=3Ais1vGVDns6QpjA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Here's the fix:
https://github.com/pgjdbc/pgjdbc/commit/642b48a787098a6c5a068710bdbbf9f1b11f3aac
You can try it via Maven Central's <version>9.4.1208-SNAPSHOT</version>
I wonder if there is anybody from Portugal on the list?
Can you explain how you represent 2000-03-26 00:00:00?
As far as I understand, somewhere near 26th March Atlantic/Azores
skips from 00:00:00 to 01:00:00.
See http://www.timeanddate.com/time/change/portugal/ponta-delgada-azores
for 2000-03-26 00:00:00 -> 01:00:00
This causes troubles since java.util.Date is supposed to be 2000-03-26
00:00:00 Atlantic/Azores, however there is no such thing like
"2000-03-26 00:00:00 Atlantic/Azores" in Java.
If you try to use calendar.set(Calendar.HOUR_OF_DAY, 0), then you get
01:00:00 back.
This caused me to add exception to the expected results:
https://github.com/pgjdbc/pgjdbc/commit/642b48a787098a6c5a068710bdbbf9f1b11f3aac#diff-b318f589843d60530d1eada03263c1b0R895
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | Vladimir Sitnikov | 2016-01-11 22:35:00 | Re: Driver behaves differently with prepareThreshold and timestamp fields when daylights is active (was Re: Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102) |
Previous Message | Andres Freund | 2016-01-11 22:24:45 | Re: Speedup twophase transactions |