From: | Joachim Achtzehnter <joachim(at)kraut(dot)ca> |
---|---|
To: | PG Interfaces <pgsql-interfaces(at)postgresql(dot)org> |
Subject: | RE: JDBC Drop/Create problem? |
Date: | 2000-12-12 17:38:41 |
Message-ID: | Pine.LNX.4.21.0012120930300.19663-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:
>
> Unless 7.1 now supports statement level aborts (and it's possible I've
> missed it if it has) this is where the problem lies. The backend
> currently does abort the whole transaction.
Exactly. I was speaking about postgresql in general, not JDBC specificly.
In my previous email I was merely pointing out that if postgresql, i.e.
the backend, did support statement-level aborts (which it doesn't
currently) then JDBC could too. There are no special JDBC issues that
would require aborting the whole transaction.
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 | Tom Lane | 2000-12-12 17:55:17 | Re: Error message: "my bits moved right off the end of the world!" |
Previous Message | Oliver Elphick | 2000-12-12 17:37:49 | Re: PgAccess error |