>This normally should work (calling con.setAutoCommit(false);) for large
>objects.
It turns out the setAutoCommit(false) was getting eaten in the J2EE
app server (Orion, i.e. Oracle 9iAS) which tends to do its own thing
with connections, so only the first call to setAutoCommit after
getting the C
try { con.setAutoCommit(true); } catch ( Exception ignored ) {}
...
}
---
Regards,
Joe
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 12 July 2001 5:39 AM
> To: Dejan Vucinic
> Cc: [EMAIL PROTECTED]
> Subject: Re: [JDBC]
"Dejan Vucinic" <[EMAIL PROTECTED]> writes:
>> From: Tom Lane <[EMAIL PROTECTED]>
>> Probably you are not wrapping the operation into a transaction
>> (BEGIN/COMMIT). Large object descriptors are only good to the end of
>> the current transaction.
> I believe I am, the code looks like this:
>
>"Dejan Vucinic" <[EMAIL PROTECTED]> writes:
> > I'm trying to create a BLOB with the 7.1.2 JDBC driver and both
> > setBytes() and setBinaryStream() fail with this message:
> > FastPath call returned ERROR: lo_write: invalid large obj descriptor
>(0)
>From: Tom Lane <[EMAIL PROTECTED]>
>Prob
"Dejan Vucinic" <[EMAIL PROTECTED]> writes:
> I'm trying to create a BLOB with the 7.1.2 JDBC driver and both
> setBytes() and setBinaryStream() fail with this message:
> FastPath call returned ERROR: lo_write: invalid large obj descriptor (0)
Probably you are not wrapping the operation into a
Greetings,
I'm trying to create a BLOB with the 7.1.2 JDBC driver and both
setBytes() and setBinaryStream() fail with this message:
FastPath call returned ERROR: lo_write: invalid large obj descriptor (0)
Any ideas?
Thanks,
--dv
_
