Sender: arkin@arkin.exoffice.com
Message-ID: <384FF178.FA37B01F@exoffice.com>
Date: Thu, 09 Dec 1999 10:14:16 -0800
From: Assaf Arkin <arkin@exoffice.com>
Organization: Exoffice
MIME-Version: 1.0
To: Peter Mount <petermount@it.maidstone.gov.uk>
CC: pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] Transaction support in 6.5.3/JDBC
References: 
 <1B3D5E532D18D311861A00600865478C70BF1A@exchange1.nt.maidstone.gov.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> PM: Hmmm, in theory if a transaction is in a dead state (ie: an SQL
> statement failed, so anything else is ignored until the rollback), there
> should be a message in the notify queue. Our JDBC driver keeps these in
> the warnings queue, so you could read them prior to calling commit()
> yourself.

From what I gather if an SQL statement failed, the CompletedResponse
will show *ABORT STATUS*. That's an easy modification. I'm not sure
about a warning being sent, I need to figure how to test this one.

The BE also returns the name of the cursor. I assume this one should be
returned from ResultSet.getCursorName()?

arkin


> 
> arkin
> 
> --
> ____________________________________________________________
> Assaf Arkin                               arkin@exoffice.com
> CTO                                  http://www.exoffice.com
> Exoffice, The ExoLab Company             tel: (650) 259-9796
> 
> ************
> 
> ************

-- 
____________________________________________________________
Assaf Arkin                               arkin@exoffice.com
CTO                                  http://www.exoffice.com
Exoffice, The ExoLab Company             tel: (650) 259-9796