The new default mapping uses columns of SQL type "OID" to store
Java objects, and that has been tested successfully with PostgreSQL 7.02
(with JDBC type JAVA_OBJECT).
Aaron
On Tue, 31 Oct 2000, Marco wrote:
> I have this exception trying to access Object stored in a PostgreSQL table field:
>
> [MachineBean] java.rmi.ServerException: Store failed; nested exception is:
> [MachineBean] Unknown Types value.
> [MachineBean] Unknown Types value.
> [MachineBean] at org.postgresql.jdbc2.PreparedStatement.setObject(PreparedStat
> ement.java:492)
> [MachineBean] at org.postgresql.jdbc2.PreparedStatement.setObject(PreparedStat
> ement.java:498)
> [MachineBean] at org.jboss.minerva.jdbc.PreparedStatementInPool.setObject(Prep
> aredStatementInPool.java:281)
>
> Seen that table were not created by JBoss using mapping (SQL) BLOB- (JDBC) BLOB I
>had to change it using (SQL) OID or
> (SQL) BYTEA. But I had always the same troubles with exception above.
> I think exception I had is caused by a wrong mapping for java.lang.Object.
>
> I found in JBoss-user Archive this mail:
>
> PostgreSQL BLOB support is quite limited via the JDBC driver at the moment,
> in that you need to (as far as I've ever found) have the BLOB as a file
> first on the Unix box and then import it as a large object. I've installed
> Interbase 6.0b (open source) as an alternative for blob-type scenarios and
> it's working very well.
>
> Could anyone better explain to me what I can do? How can I import a file as large
>Object? And how to create a file from the BLOB?
>
> Thanks a lot.
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
