Re: binary data in `bytea' column

From: Anton Komarevtsev <avkx(at)rt(dot)mipt(dot)ru>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: binary data in `bytea' column
Date: 2004-04-20 05:37:36
Message-ID: 4084B720.9010103@rt.mipt.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Oliver Jowett wrote:
> Anton Komarevtsev wrote:
>
<skipped>
>
>> I use Postgres 7.4, and autocommit=on is hardcoded in it.
>
>
> 7.4 doesn't support autocommit=off on the server side, as I understand
> it -- is this what you mean?
>
Yes, it is what I mean.

>> But I've listened, that Large Objects may only work in a single
>> transaction. So, if I should use Large Objects (if so), how should I
>> use them?
>
>
> You can still change the JDBC-level autocommit setting safely (via
> Connection.setAutoCommit) regardless of the server's autocommit
> capabilities.

Unfortunately, java.sql.Connection.setAutoCommit(false) hangs current
java thread without some exceptions.

>
> -O
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2004-04-20 05:49:17 Re: binary data in `bytea' column
Previous Message Tom Lane 2004-04-20 04:15:05 Re: EXECUTE command tag returns actual command