Re: can't write a BLOB, 7.1.2 - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: can't write a BLOB, 7.1.2
Date
Msg-id 3258.994880335@sss.pgh.pa.us
Whole thread Raw
In response to Re: can't write a BLOB, 7.1.2  ("Dejan Vucinic" <hotdejan@hotmail.com>)
List pgsql-jdbc
"Dejan Vucinic" <hotdejan@hotmail.com> writes:
>> From: Tom Lane <tgl@sss.pgh.pa.us>
>> 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:

>   connection.setAutoCommit(false);
>   insert = connection.prepareStatement(
>              "INSERT INTO FOO (A, B) VALUES (?, ?)");
>   insert.setString(1, somestring);
>   insert.setBytes(2, byte[] xx);
>   insert.executeUpdate();
>   connection.commit();
>   connection.setAutoCommit(true);

I have no idea what that actually does at the database level.
In particular, does the setAutoCommit(false) routine send a
BEGIN, or does it only set some state that affects later operations?
If there's not a BEGIN sent before the LO operations, they'll fail.

You might try turning on query logging at the postmaster to see
what requests are really being transmitted.

            regards, tom lane

pgsql-jdbc by date:

Previous
From: "Dejan Vucinic"
Date:
Subject: RE: [PATCH] setTimestamp(int, Timestamp) fails on null timestamp
Next
From: Joseph Shraibman
Date:
Subject: Re: jdbc and unix signals