| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Anton Komarevtsev <avkx(at)rt(dot)mipt(dot)ru> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: binary data in `bytea' column |
| Date: | 2004-04-20 05:49:17 |
| Message-ID: | 4084B9DD.8050606@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Anton Komarevtsev wrote:
> Oliver Jowett wrote:
>> 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.
I'm not sure what you mean. Could you post a testcase demonstrating the
problem you see? setAutoCommit() *should* work fine, assuming you are
using at least a 7.4 driver (a 7.3 driver against a 7.4 server is
unlikely to work, however).
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Robinson | 2004-04-20 15:35:39 | Re: Prepared Statements and large where-id-in constant blocks? |
| Previous Message | Anton Komarevtsev | 2004-04-20 05:37:36 | Re: binary data in `bytea' column |