| From: | Till Toenges <tt(at)kyon(dot)de> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| 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:39:49 |
| Message-ID: | 47BA95D5.40408@kyon.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
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.
Till
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2008-02-19 08:41:10 | Re: Implementing setQueryTimeout() |
| Previous Message | Oliver Jowett | 2008-02-19 08:30:11 | Re: Implementing setQueryTimeout() - round 2 |