I noticed if I have a long running SQL and want to cancel it, clicking
on "Cancel SQL" will not cancel it, the SQL continues to run.

Dave

Dave,

<< I noticed if I have a long running SQL and want to cancel it, clicking on
"Cancel SQL" will not cancel it, the SQL continues to run. >>

What is the nature of the SQL being executed ?  The type of SQL statement
combined with the progress interval could result in a bit of time before the
actual execution stops in some cases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:
> Dave,
>
> << I noticed if I have a long running SQL and want to cancel it, clicking on
> "Cancel SQL" will not cancel it, the SQL continues to run. >>
>
> What is the nature of the SQL being executed ?  The type of SQL statement
> combined with the progress interval could result in a bit of time before the
> actual execution stops in some cases.
>
It was a "Select * from table". I cancelled it and several minutes later
it was still running.

Dave

Dave,

<< It was a "Select * from table". I cancelled it and several minutes later
it was still running. >>

Okay, I will check it out and make sure that it is operational for 1.06.  I
haven't been able to confirm what you're saying here yet, but if it is
having an issue, then I'll put in an incident report for it.

--
Tim Young
Elevate Software
www.elevatesoft.com

<< Okay, I will check it out and make sure that it is operational for 1.06.
I haven't been able to confirm what you're saying here yet, but if it is
having an issue, then I'll put in an incident report for it. >>

I found the issue - an abort of the query is causing change detection to
fire for the query and causing a refresh of the query.  Essentially, the
query ends up running twice in such a case.

--
Tim Young
Elevate Software
www.elevatesoft.com