Re: binary data in `bytea' column
От | Anton Komarevtsev |
---|---|
Тема | Re: binary data in `bytea' column |
Дата | |
Msg-id | 4084B720.9010103@rt.mipt.ru обсуждение исходный текст |
Ответ на | Re: binary data in `bytea' column (Oliver Jowett <oliver@opencloud.com>) |
Ответы |
Re: binary data in `bytea' column
|
Список | 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 >
В списке pgsql-jdbc по дате отправления: