Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] JDBC (executing transactions coding style)

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: Constantin Teodorescu <teo(at)flex(dot)ro>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Re: [INTERFACES] JDBC (executing transactions coding style)
Date: 1999-04-15 14:07:32
Message-ID: 3715F2A4.2C2C4C17@alumni.caltech.edu (view raw or flat)
Thread:
Lists: 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

pgsql-interfaces by date

Next:From: Ari HalberstadtDate: 1999-04-15 15:45:31
Subject: Re: [INTERFACES] JDBC (executing transactions coding style)
Previous:From: Peter MountDate: 1999-04-15 13:49:01
Subject: RE: [INTERFACES] JDBC (executing transactions coding style)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group