| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | taktos <taktos(at)gmail(dot)com>, Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: commit and rollback don't throw exceptions when they should |
| Date: | 2009-11-19 00:59:57 |
| Message-ID: | alpine.BSO.2.00.0911181943340.26932@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, 18 Nov 2009, Kevin Grittner wrote:
> That all makes sense. I think you have a copy/paste error in the
> exception message, though: "This statement has been closed." It is
> the connection which has been closed here.
Doh! Fixed.
> Also, for software which tries to make sense of the SQLSTATE for
> automated handling, I'm inclined to think that something in Class Code
> '08' (Connection Exception) would be more useful than the Class Code
> '55' (Object Not in Prerequisite State) value. Granted, it's a gray
> area, since the problem with the connection is that it's not in an
> open state....
I've changed it to 08003 CONNECTION_DOES_NOT_EXIST. We're already using
it for this purpose (already closed) in the connection pooling code.
Thanks for following up on this.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-11-19 17:01:18 | Re: commit and rollback don't throw exceptions when they should |
| Previous Message | Kevin Grittner | 2009-11-18 19:31:32 | Re: commit and rollback don't throw exceptions when they should |