From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Vaibhav Nivargi <vaibhav(dot)nivargi(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Potential inconsistency in handling of timestamps |
Date: | 2007-10-25 22:18:32 |
Message-ID: | 47211638.2080404@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Vaibhav Nivargi wrote:
> Hi,
> I am using PG-jdbc-8.2-506 to connect to a Postgres DB with a table
> containing a timestamp column. Some entries for this are null. When I
> try to retrieve the entries, I get a Bad Value PSQLException for rows
> which have the timestamp set to null. I was able to trace it to
> org/postgresql/jdbc2/Timestamputils.java: loadCalender() which
> explicitly checks whether the timestamp has either a date or time
> value, else throws an exception.
>
> OTOH, setting a timestamp to null through jdbc (Update stmt) works
> without error. This seems like inconsistent behavior.
>
> Am I missing something? Any special settings for handling null
> timestamp/date values?
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?
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2007-10-25 22:23:29 | Re: Potential inconsistency in handling of timestamps |
Previous Message | Vaibhav Nivargi | 2007-10-25 22:00:11 | Potential inconsistency in handling of timestamps |