From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: patch: streaming of bytea parameter values |
Date: | 2004-05-23 22:25:51 |
Message-ID: | 40B124EF.1040000@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Kris Jurka wrote:
>>Being user-friendly when dealing with application errors is nice
>>behaviour to have, but it *is* a separate issue..
>
>
> Separate from what, correctness?
Yes.
> We both agree that a short stream or
> IOException is an error, but I'm not advocating the JDBC equivalent of
> System.exit() as a viable solution. What makes it OK for this
> particular error to destroy a Connection while no other application level
> error can?
The implementation of SQLState (or connectionErrorOccurred) across
different drivers is quite patchy. When writing portable applications
(or even driver-specific applications, to a lesser extent) you have to
assume that any SQLException you don't specifically recognize means your
connection is toast.
I don't see that tearing down the connection for a certain class of
hard-to-handle errors makes this situation any worse.
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2004-05-24 06:38:40 | Re: Result Set Cursor Patch |
Previous Message | Oliver Jowett | 2004-05-23 22:17:20 | Re: patch: streaming of bytea parameter values |