Re: Potential inconsistency in handling of timestamps - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: Potential inconsistency in handling of timestamps
Date
Msg-id Pine.BSO.4.64.0710251829240.29225@leary.csoft.net
Whole thread Raw
In response to Re: Potential inconsistency in handling of timestamps  (Oliver Jowett <oliver@opencloud.com>)
Responses Re: Potential inconsistency in handling of timestamps  (Oliver Jowett <oliver@opencloud.com>)
List 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

pgsql-jdbc by date:

Previous
From: Frank Habermann
Date:
Subject: multiple connections to db over jsp
Next
From: "Brad Larson"
Date:
Subject: Calling a stored procedure with a custom return type