![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
![]() |
Thu, Sep 13 2007 12:51 PM | Permanent Link |
Dave Harrison | 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 |
Thu, Sep 13 2007 3:27 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | 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 |
Thu, Sep 13 2007 3:28 PM | Permanent Link |
Dave Harrison | 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 |
Fri, Sep 14 2007 2:53 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | 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 |
Fri, Sep 14 2007 3:19 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | << 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 |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |