Hi Jan Yes, that was the workaround I posted a while ago. Now, why didn't I think of searching previous posts...
You could either take the same approach or follow Ned's advise and try out the latest drivers. Keith -----Original Message----- From: Jan Kanzleiter [mailto:[EMAIL PROTECTED]] Sent: Friday, 25 January 2002 9:57 p.m. To: [EMAIL PROTECTED] Subject: Re: [castor-dev] postgresql and large objects hi, On Fri, Jan 25, 2002 at 01:38:03PM +1300, Keith Chew wrote: > 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(). ah, then an other jdbc driver would help me? > Basically, I used another > setObject() in Castor that the postgresql JDBC driver supports. do you talk about this patch? http://castor.exolab.org/list-archive/msg10841.html > I'll dig around later and get back to you if I find it. that would be really cool. thanks a lot for your help 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
