Re: Potential inconsistency in handling of timestamps

From: Kris Jurka <books(at)ejurka(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Vaibhav Nivargi <vaibhav(dot)nivargi(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Potential inconsistency in handling of timestamps
Date: 2007-10-25 22:30:51
Message-ID: Pine.BSO.4.64.0710251829240.29225@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Fri, 26 Oct 2007, Oliver Jowett wrote:

>> Null values should in theory get handled and returned well before
>> TimestampUtils ever gets invoked (see
>> AbstractJdbc2ResultSet.getTimestamp()). Can you supply a testcase
>> demonstrating the problem?
>
> Actually, it looks like this was fixed in AbstractJdbc2ResultSet r1.95
> (I was looking at CVS HEAD) but not on the 8.2 branch.
>

I don't follow. The commit you mention was unify the handling of the
RS.wasNull flag, not changing the handling of null values. That should be
caught in TimestampUtils.toTimestamp and friends.

Kris Jurka

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Brad Larson 2007-10-25 22:32:38 Calling a stored procedure with a custom return type
Previous Message Oliver Jowett 2007-10-25 22:23:29 Re: Potential inconsistency in handling of timestamps