From: | Joachim Achtzehnter <joachim(at)kraut(dot)ca> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | RE: JDBC Drop/Create problem? |
Date: | 2000-12-11 17:29:22 |
Message-ID: | Pine.LNX.4.21.0012110922080.18977-100000@penguin.kraut.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Today, in a message to pgsql-interfaces, Peter Mount wrote:
>
> The problem JDBC has is that it's DatabaseMetaData methods can make
> several queries. While AutoCommit is off, if one of those fails, the
> users transaction will also fail.
If the JDBC driver under the hood performs several queries in response to
a single 'user command' and one of these fails it can still report that
command's failure without aborting the whole transaction (assuming the
backend supports statement-level aborts, of course).
Joachim
--
work: joachima(at)realtimeint(dot)com (http://www.realtimeint.com)
private: joachim(at)kraut(dot)ca (http://www.kraut.ca)
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Kachnowich | 2000-12-11 17:29:36 | RE: JDBC Timestamp Problem |
Previous Message | Peter Eisentraut | 2000-12-11 17:20:20 | Re: [PATCHES] ODBC Driver patch |