From: books at ejurka.com (Kris Jurka)
Date: Fri, 1 Feb 2008 00:09:25 -0500 (EST)
Subject: [Pljava-dev] R:  select CURRENT_TIMESTAMP is wrong
In-Reply-To: <Pine.BSO.4.64.0801250502210.7084@leary.csoft.net>
References: <014401c85dbc$477601d0$16b0a8c0@ASUSSTEFANO>
	<09DA7761-B2E9-4036-B2B1-84F97418F3D4@mac.com>
	<014901c85dbf$c92040d0$16b0a8c0@ASUSSTEFANO>
	<227D74A0-C160-4036-ABBD-75D08B65C44A@mac.com>
	<A38F63DA-3A61-4796-8952-7D699433D5B2@mcsnw.com>
	<Pine.BSO.4.64.0801250502210.7084@leary.csoft.net>
Message-ID: <Pine.BSO.4.64.0802010007390.26244@leary.csoft.net>



On Fri, 25 Jan 2008, Kris Jurka wrote:

> On Fri, 25 Jan 2008, Lucas Madar wrote:
>
>> I didn't post this to the list by mistake, but I found a solution. It appears
>> that some precision is being lost with certain compilers. The culprit is
>> this:
>>       mSecs += EPOCH_DIFF * 1000;                     /* Adjust for diff
>> between Postgres and Java (Unix) */
>>

This is not compiler dependent, it just depends on whether this code is 
used or not.  This function is only used when running against a server 
built with integer datetimes.

Fixed in CVS.

Kris Jurka