You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "sagar (JIRA)" <ji...@apache.org> on 2018/08/04 12:25:00 UTC

[jira] [Commented] (DERBY-3908) Add a mechanism for cancelling runaway transactions.

    [ https://issues.apache.org/jira/browse/DERBY-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569172#comment-16569172 ] 

sagar commented on DERBY-3908:
------------------------------

Any progress on this issue?

This is required.

If I use a client like Squirrel SQL to query and administer derby then some times on recursive indeterminate selects I try to cancel the statement but it says either not implemented or underlying driver does not support the cancelstatement function.

> Add a mechanism for cancelling runaway transactions.
> ----------------------------------------------------
>
>                 Key: DERBY-3908
>                 URL: https://issues.apache.org/jira/browse/DERBY-3908
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Rick Hillegas
>            Priority: Major
>              Labels: derby_triage10_10
>
> We should add a mechanism by which the DBA can cancel a runaway transaction. Perhaps we could implement this as a new system procedure. This issue comes up on the user list frequently. For instance, see this thread: http://www.nabble.com/cancel-a-running-query--td19903183.html#a19903183 On the implementation side, Knut points out that EmbedConnection.cancelRunningStatement() might be a useful place to start.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)