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:43:59
Message-ID: Pine.BSO.4.64.0710251840250.18159@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Fri, 26 Oct 2007, Oliver Jowett wrote:

> You're right though, null should be caught by TimestampUtils.toTimestamp()
> too.
>
> Back to looking for a testcase?
>

Indeed. Personally I suspect he doesn't have a timestamp column, but
something textual and is confused over the difference between NULL and ''.
Even without a testcase, the complete error message and stack trace should
include the value he's actualy dealing with and where the driver had
trouble with it.

Kris Jurka

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2007-10-25 22:47:48 Re: Calling a stored procedure with a custom return type
Previous Message Oliver Jowett 2007-10-25 22:37:20 Re: Potential inconsistency in handling of timestamps