Re: TIMESTAMP value binary transfer problem

There was a problem with some time zones from memory, in the uk for example 1970 had an odd daylight saving period and because 1970 is used in calculating the time values in the driver this skews the results in the driver. Using the current year fixes it when calculating times.

Maybe something to check.

On 25 October 2014 19:21:25 GMT+01:00, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>This is the same as https://github.com/pgjdbc/pgjdbc/pull/133
>
>So what I am wondering is why a small number of people see this and the
>rest are fine ???
>
>What is unique about your environment. Are the server and the client on
>the
>same timezone ?
>
>Dave Cramer
>
>dave.cramer(at)credativ(dot)ca
>http://www.credativ.ca
>
>On 22 October 2014 14:03, Vladimir Crnčić (Infoart d.o.o.) <
>vcrncic(at)infoart(dot)hr> wrote:
>
>> There is a problem with JDBS driver interpretation of "timestamp
>without
>> time zone" values when binary transfer is on. When binary transfer is
>> disabled for TIMESTAMP columns (binaryTransferDisable=TIMESTAMP or
>> binaryTransfer=false) problem does not occur.
>>
>>
>>
>> database version: 9.1.1
>>
>> driver version: 9.2, 9.3
>>
>>
>>
>> BINARY TRANSFER:
>>
>> ----------------
>>
>> database value (TIMESTAMP): 2014-10-26 01:00:04
>>
>> bytes (AbstractJdbc2Resultset): [0, 1, -87, 71, -77, -6,
>45,
>> 0]
>>
>> long value (TimestampUtils): 467600404000000
>>
>> java timestamp (TimestampUtils): 2014-10-26
>> 02:00:04.0 (not OK)
>>
>>
>>
>> TEXT TRANSFER:
>>
>> --------------
>>
>> database value (TIMESTAMP):
>2014-10-26
>> 01:00:04
>>
>> string value (AbstractJdbc2Resultset): 2014-10-26
>01:00:04
>>
>> java timestamp (TimestampUtils): 2014-10-26
>> 01:00:04.0 (OK)
>>

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.