Re: BUG #2882: jdbc driver: date returned from a stored proc is incorrect

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Ravi <ravitx12(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2882: jdbc driver: date returned from a stored proc is incorrect
Date: 2007-01-12 00:38:33
Message-ID: 20070112003833.GJ10464@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ravi wrote:

> On Red Hat Enterprise Linux AS release 4 (Nahant Update 3) the milliseconds
> returned is as follows
>
> -2209028400000 = -25567.458333333333333333333333333 = Jan 1 1900
>
> On Red Hat Enterprise Linux AS release 3 (Taroon Update 3) the milliseconds
> returned is as follows
> -2208952800000 = -25566.583333333333333333333333333 = Jan 2 1900

Is one of these compiled with --enable-integer-datetimes, and the other
not? You can tell by calling pg_controldata, IIRC.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2007-01-12 03:57:13 Re: BUG #2879: RPM: wrong quoting of error message about old database format after upgrading
Previous Message Christopher Brian Jurado 2007-01-11 23:17:26 BUG #2883: TCP Keep Alive not enabled even after setting it in postresql.conf