I got this also,
The problem is with the implementation of getDate() in the PostGres
Drivers. It is a very big hassle to fix. It throws a parse exception
when trying to do a SimpleDateFormat on the String coming from the
Database.
Once i fixed that, I also ran into a problem where it seems that orion
already has a version of the postgres drivers internally somewhere, so my
.jar file with the fix was not being picked up by orion. I ended up
having to change the package name of all the classes in the Postgres
drivers, and use a different one.
I'll attach the one I am using, but my fix is not particularly
robust. All i did was put in a couple of conditions on the string, and
catch the parseFormat error.
If you want to fix the problem yourself, it's on line 447 of the
ResultSet.java file in jdbc2, of the postgres JDBC drivers that come with
the database.
I had a bunch of other problems with the Postgres drivers, I never got
large objects to work through CMP, and one of the features of JDBC2,
setFetchSize(int) throws a "Not Implemented" exception. :-P
Best of luck,
-Lkb
On Mon, 18 Sep 2000 [EMAIL PROTECTED] wrote:
> I have an entity bean that contains a java.util.Date property. Creating
> works fine, but when I using a finder method, I get the following error:
>
> com.evermind.server.rmi.OrionRemoteException: Database error: Bad Timestamp
> Format at 19 in 2000-09-18 14:08:47.86-04; nested exception is:
> Bad Timestamp Format at 19 in 2000-09-18 14:08:47.86-04
>
> Has anyone seen this before using java.util.Date, CMP, orion and Postgres?
>
postgres.tar.gz
r6_postgres.jar
