| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Oliver Jowett" <oliver(at)opencloud(dot)com> |
| Cc: | "Till Toenges" <tt(at)kyon(dot)de>, "PostgreSQL - JDBC" <pgsql-jdbc(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Implementing setQueryTimeout() - round 2 |
| Date: | 2008-02-19 09:46:28 |
| Message-ID: | 87ve4lz3bf.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
"Oliver Jowett" <oliver(at)opencloud(dot)com> writes:
> The real world case I am dealing with needs the hardQueryTimeout behaviour. If
> I'm going to implement anything first, it's that.
I still don't understand why this has to be in the driver. Your application is
going to have to be able to handle creating a new connection in response to
this error so why can't it just also be the one to close the connection?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2008-02-19 10:01:14 | Re: Implementing setQueryTimeout() - round 2 |
| Previous Message | Till Toenges | 2008-02-19 09:13:37 | Re: Implementing setQueryTimeout() |