| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Till Toenges <tt(at)kyon(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Implementing setQueryTimeout() |
| Date: | 2008-02-19 08:41:10 |
| Message-ID: | 47BA9626.5060209@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Till Toenges wrote:
> Oliver Jowett wrote:
>>> A network timeout or anything worse is handled in an entirely
>>> different part of the code. That is not the responsibility of the
>>> driver, and doesn't event need to be part of the database related
>>> code at all.
>>
>> I'm not sure what you mean here - if the connection to the DB fails,
>> the driver will certainly handle that and tell you about it via a
>> SQLException!
>
> Sorry. Of course the driver must handle failed connections. I meant the
> code in my application, which handles the two cases (timeout but usable
> connection vs broken connection for whatever reason) differently.
You can check the SQLState of any exception thrown to tell the
difference, right?
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2008-02-19 08:46:38 | Re: Implementing setQueryTimeout() |
| Previous Message | Till Toenges | 2008-02-19 08:39:49 | Re: Implementing setQueryTimeout() |