Thank you for handling that. I'll update the test cases to a) make sure
the right driver is available b) schema uses bytea and the docs so that
others know that this can be done.
Thanks again.
On Sat, 2002-02-02 at 18:34, Jan Kanzleiter wrote:
> hi,
>
> i only want to say thank you to all the
hi,
i only want to say thank you to all the people on the list who helped me
with the postgresql and large object problem - it is resolved now.
i use "bytea" instead of "oid" in postgresql 7.1.3. As jdbc-driver i use
the jdbc7.2dev-1.2.har from jdbc.postgresql.org.
the mapping for the field i
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 th
You may want to try the latest jdbc driver for postgresql from
jdbc.postgresql.org. The ones that have been distributed in postgresql
in 7.1.3 and eariler releases have had problems with this. Keep in mind
that the new driver uses columns of type bytea instead of type oid for
large object suppor
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 driv
2 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:
hi,
the next question:
there is no blob-type in postgresql like in mysql. because of that normally
you can use the type OID.
how can i use this type in castor. (mapping.xml).
thanks for helping me
jan
---
If you wish to unsubscribe fro
