Received: from localhost (IDENT:root@hectic-3.jpl.nasa.gov [128.149.68.205]) by hub.org (8.9.2/8.9.1) with ESMTP id KAA91118 for ; Thu, 15 Apr 1999 10:07:43 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id OAA31404; Thu, 15 Apr 1999 14:07:32 GMT Sender: lockhart@hub.org Message-ID: <3715F2A4.2C2C4C17@alumni.caltech.edu> Date: Thu, 15 Apr 1999 14:07:32 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Constantin Teodorescu CC: PostgreSQL Interfaces Subject: Re: [INTERFACES] JDBC (executing transactions coding style) References: <3715C329.9739047D@flex.ro> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > 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