Re: Bad Value for Data Type Timestamp

From: Kris Jurka <books(at)ejurka(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Bad Value for Data Type Timestamp
Date: 2006-04-29 02:34:22
Message-ID: Pine.BSO.4.63.0604282134030.21839@leary2.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Wed, 1 Mar 2006, Oliver Jowett wrote:

> Jonathan Vallar wrote:
>
>> Retrieve Operation failed on the BusinessObject Bad value for type
>> timestamp : [C(at)56c55d28 Exception: java.lang.NumberFormatException:
>> Expected time to be colon-separated, got ' Stack Trace:
>> java.lang.NumberFormatException : Expected time to be colon-separated, got
>> ' at [...]
>
> Hmm, loadCalendar() should put the original string in the exception message,
> not the char-array-ified version which produces that useless [C(at)(dot)(dot)(dot)(dot) thing :(
>

Done.

Kris Jurka

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message David Blasby 2006-05-01 22:05:07 Re: OutOfMemory causing connection leaks
Previous Message Kris Jurka 2006-04-29 02:20:05 Re: gcj has a lot of complaints about 8.1-405 release