From: | Assaf Arkin <arkin(at)exoffice(dot)com> |
---|---|
To: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
Cc: | pgsql-interfaces(at)hub(dot)org |
Subject: | Re: [INTERFACES] Transaction support in 6.5.3/JDBC |
Date: | 1999-12-09 18:14:16 |
Message-ID: | 384FF178.FA37B01F@exoffice.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
> 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(at)exoffice(dot)com
> CTO http://www.exoffice.com
> Exoffice, The ExoLab Company tel: (650) 259-9796
>
> ************
>
> ************
--
____________________________________________________________
Assaf Arkin arkin(at)exoffice(dot)com
CTO http://www.exoffice.com
Exoffice, The ExoLab Company tel: (650) 259-9796
From | Date | Subject | |
---|---|---|---|
Next Message | Assaf Arkin | 1999-12-09 18:42:43 | Re: [INTERFACES] Transaction support in 6.5.3/JDBC |
Previous Message | Hiroki Kataoka | 1999-12-09 14:53:25 | Re: ODBC and Large Objects, FAQ not working |