Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-jdbc by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group