From: | Florent Guillaume <fg(at)nuxeo(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Improvements for statement cancellation |
Date: | 2013-04-12 10:21:44 |
Message-ID: | CAF-4BpOwL=Oz_mG=auSoEcuDRVoAJNXOMH+8i2oFORJEMs5cJg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, Apr 12, 2013 at 4:32 AM, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com> wrote:
>> I'm wondering if it's possible if Postgres JDBC could change the
>> implementation of cancel() so that cancelQuery() is only sent if
>> the statement being called is the actual statement that is being
>> executed on the connection, and otherwise be a no-op.
>
> I wondered the same thing back in 2005:
> http://www.postgresql.org/message-id/438F2DE5.EE98.0025.0@wicourts.gov
> I still think that something of the sort would be a good idea.
Agreed, the current Statement.cancel() behavior can only be described as buggy.
Florent
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
From | Date | Subject | |
---|---|---|---|
Next Message | Nicholas White | 2013-04-12 15:52:25 | Re: Patch: Force Primitives |
Previous Message | Kevin Grittner | 2013-04-12 02:32:54 | Re: Improvements for statement cancellation |