From: | Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> |
---|---|
To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
Cc: | Tore Halset <halset(at)pvv(dot)ntnu(dot)no>, pgsql-general(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: [JDBC] ERROR: canceling query due to user request |
Date: | 2004-09-09 10:42:42 |
Message-ID: | 20040909114242.A1057@bacon |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
On 09/09/2004 10:41 Oliver Jowett wrote:
> Paul Thomas wrote:
>
>> Given that statement.cancel() should only be used to cancel a running
>> query, I think the problem is more in your framework's misuse of
>> cancel() rather than in the driver itself.
>
> JDBC gives you no way to ensure you only call cancel() on a running query
> (there's a race between query execution returning and the call to
> cancel()). Calling cancel() on a statement that's not currently executing
> should do nothing; if it ends up cancelling a future query, it's a driver
> bug.
Thanks for the explaination Oliver. Maybe there is a driver bug then?
--
Paul Thomas
+------------------------------+-------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for Business |
| Computer Consultants | http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+-------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2004-09-09 11:41:27 | Re: Migrating from MaxDB to postgresql |
Previous Message | Oliver Jowett | 2004-09-09 09:41:07 | Re: [JDBC] ERROR: canceling query due to user request |
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre-Frédéric Caillaud | 2004-09-09 12:56:35 | Byte Sizes |
Previous Message | Oliver Jowett | 2004-09-09 09:41:07 | Re: [JDBC] ERROR: canceling query due to user request |