| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "David Fetter" <david(at)fetter(dot)org>, "PG Hackers" <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL JDBC List" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Date: | 2010-10-11 13:29:16 |
| Message-ID: | 4CB2CADC020000250003676B@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
David Fetter <david(at)fetter(dot)org> wrote:
> Please find enclosed a WIP patch from one of my co-workers
> intended to support JDBC's setQueryTimeout, along with the patch
> for JDBC that uses it.
I agree that it would be very nice to support this JDBC feature, but
I'm not clear on why this can't be done with just JDBC changes using
the java.util.Timer class and the existing Statement.cancel()
method. Can you explain why the backend needed to be touched?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Kupershmidt | 2010-10-11 13:41:35 | Re: column-level update privs + lock table |
| Previous Message | Leonardo Francalanci | 2010-10-11 13:20:29 | On the usefulness of hint bits |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-11 14:17:24 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Previous Message | Delpierre, David | 2010-10-11 08:19:22 | JDBC compatibility |