I stand corrected. Last time I looked, which actually was longer ago
than it seemed - time flies, the setBinaryStream() threw the exception
directly. When people in our organization tried out new versions they
informed me that the code had changed, but it still didn't work. My bad.
/Marcus
On
A _very_ late answer I know, but it is my firm belief that the reason
for this is that Postgresql JDBC driver does not support BLOB:s, it is
simply not implemented, hence the message. Check out the WebCVS and see
for yourselves.
/Marcus
On Fri, 2001-06-22 at 20:42, Phillip Ross wrote:
Your
Actually the Postgres driver does support blobs in a number of ways. The
7.1 driver supports BLOBs using OIDs (a postgres specific measure) and
the latest driver from CVS (due out with 7.2 shortly) supports bytea
datatypes (which is a long byte array up to 1 gig in size) which is much
nicer than
Your problem is stemming from the fact that the Postgresql JDBC driver wants
auto commit flag set to false before it can use setBinaryStream() method which
is used to store the stream. Orion's entity bean wrapper seems to leave the
flag alone and not set it to false explicitly. So, basicly,
