Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <5654784.317461294853505676.JavaMail.jira@thor>
Date: Wed, 12 Jan 2011 12:31:45 -0500 (EST)
From: "Dag H. Wanvik (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-4968) Let query stop execution if an
 interrupt is seen, at same time as we check the query timeout
In-Reply-To: <12471082.294171294777605721.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-4968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dag H. Wanvik reassigned DERBY-4968:
------------------------------------

    Assignee: Dag H. Wanvik

> Let query stop execution if an interrupt is seen, at same time as we check the query timeout
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4968
>                 URL: https://issues.apache.org/jira/browse/DERBY-4968
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>             Fix For: 10.8.0.0
>
>         Attachments: derby-4968-1.diff, derby-4968-1.stat
>
>
> Subtask of DERBY-4741. 
> In BasicNoPutResultSetImpl#checkCancellationFlag we currently check whether a statement has been canceled or it timed out at certain times during query execution. We would like an interrupt seen during execution hitherto to also throw at this point. Cf the way we also stop execution of batches if a batch element sees an interrupt.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.