#1082 Cancelling statements is not working like it should


While the app is building output, it should be possible to cancel the query regardless of the server - building output happens locally, not on server (as far as I understand). Or if not, the status of the query should maybe be more detailed, like "receiving data from server", "building output" etc and the cancel button would do different things on different statuses. Currently for example when I have a large query result (100s of 1000s of rows) and I do not manually limit it and the "Limit rows" is set to 1000, I press "cancel" occasionally if I realize I have mistaken in my SQL. Then I get a message that "Failed to cancel statement within one second. Perhaps your driver/database does not support cancelling statements. If cancelling succeeds later you'll get a further messages." but finally when I get the results, it shows 999 rows. That tells me the problem is not on the server side, it's in the app instead. The same thing happens with "Limit rows" 100 and result being 99. It's like the engine gets tired on the last mile or something. Anyway, just wanted to make the world better :)


  • sfst

    sfst - 2017-03-01

    I think this was fixed quite some time ago and can be closed now, right?

  • Gerd Wagner

    Gerd Wagner - 2017-03-04
    • status: open --> closed
  • Gerd Wagner

    Gerd Wagner - 2017-03-04

    Yes it's fixed. Thanks for the pointer.


Log in to post a comment.