| From: | fschmidt <fschmidt(at)gmail(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: committing an aborted transaction |
| Date: | 2008-11-15 22:20:34 |
| Message-ID: | 20520062.post@talk.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Tom Lane-2 wrote:
>
> This is a server-side behavior, not JDBC's fault. It's been like that
> for ten years and is unlikely to be changed. See prior discussions,
> for instance here:
>
> http://archives.postgresql.org/pgsql-bugs/2004-03/msg00179.php
> http://archives.postgresql.org/pgsql-hackers/2004-07/msg00416.php
> http://archives.postgresql.org/pgsql-hackers/2004-10/msg00908.php
>
So it seems, based on this last link, that commit now returns a "ROLLBACK"
in this case. So then why doesn't JDBC throw an exception when a commit
returns "ROLLBACK"?
--
View this message in context: http://www.nabble.com/committing-an-aborted-transaction-tp20519423p20520062.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jay Howard | 2008-11-16 02:29:40 | Re: passing user defined data types to stored procedures |
| Previous Message | Tom Lane | 2008-11-15 21:52:25 | Re: committing an aborted transaction |