Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 25 Oct 2007 18:30:51 -0400 (EDT)
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
- Follow-Ups:
- Re: Potential inconsistency in handling of timestamps
- From: Oliver Jowett
- Re: Potential inconsistency in handling of timestamps
- References:
- Potential inconsistency in handling of timestamps
- From: Vaibhav Nivargi
- Re: Potential inconsistency in handling of timestamps
- From: Oliver Jowett
- Re: Potential inconsistency in handling of timestamps
- From: Oliver Jowett
- Potential inconsistency in handling of timestamps
- Prev by Date: multiple connections to db over jsp
- Next by Date: Calling a stored procedure with a custom return type
- Previous by thread: Re: Potential inconsistency in handling of timestamps
- Next by thread: Re: Potential inconsistency in handling of timestamps
- Indexes: