Oh yeah, I think I encountered this before. It's a JDBC driver problem. If you look that the JDBC implementation, the version that you have got has removed quite a number of types in the setObject().
I did a workaround in Castor a long time ago, but can't seem to find the patch (I am no longer actively using Castor). Basically, I used another setObject() in Castor that the postgresql JDBC driver supports. I'll dig around later and get back to you if I find it. Keith -----Original Message----- From: Jan Kanzleiter [mailto:[EMAIL PROTECTED]] Sent: Friday, 25 January 2002 10:51 a.m. To: [EMAIL PROTECTED] Subject: Re: [castor-dev] postgresql and large objects hi, On Fri, Jan 25, 2002 at 09:12:44AM +1300, Keith Chew wrote: > Have you tried "varbinary": yes i did it, and i get the same exception. 2002-01-24 22:46:26 - Ctx( /people ): Exception in: R( /people + /savePeople.do + null) - Unknown Types value. at org.postgresql.jdbc2.PreparedStatement.setObject(PreparedStatement.java:552) at org.postgresql.jdbc2.PreparedStatement.setObject(PreparedStatement.java:558) at com.codestudio.sql.PoolManPreparedStatement.setObject(Unknown Source) at org.exolab.castor.jdo.engine.SQLTypes.setObject(SQLTypes.java:395) at org.exolab.castor.jdo.engine.SQLEngine.store(SQLEngine.java:793) at org.exolab.castor.persist.ClassMolder.store(ClassMolder.java:1584) greetings jan ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
