Re: [INTERFACES] JDBC (executing transactions coding style) - Mailing list pgsql-interfaces

From Thomas Lockhart
Subject Re: [INTERFACES] JDBC (executing transactions coding style)
Date
Msg-id 3715F2A4.2C2C4C17@alumni.caltech.edu
Whole thread Raw
In response to JDBC (executing transactions coding style)  (Constantin Teodorescu <teo@flex.ro>)
List pgsql-interfaces
> What I want to know : is there necessary to do a st.executeUpdate("ABORT
> TRANSACTION") in the catch instruction block ?
> I recall that someone says that an error inside a transaction block
> automatically aborts the transaction.
> Is it true ? It works here ?

Someone else probably has up to date information. I recall that if an
error happens within a BEGIN/END block, all other commands are
rejected until an END (or ABORT?) is executed. The assumption is that
if something fails within a transaction you want to rollback
everything else within that transaction, and the transaction isn't
over until you explicitly complete it.

                    - Tom

--
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California

pgsql-interfaces by date:

Previous
From: Peter Mount
Date:
Subject: RE: [INTERFACES] JDBC (executing transactions coding style)
Next
From: Ari Halberstadt
Date:
Subject: Re: [INTERFACES] JDBC (executing transactions coding style)