Run query button

BubikolRamios's profile image BubikolRamios posted 2 years ago in General Permalink

Sometimes it becomes disabled, apparent reason - query is running. It is not. One can't close that query tab either. If that could be sorted - at least closing query tab ?

ansgar's profile image ansgar posted 2 years ago Permalink

Yes I also saw that one time, just don't recall how to reproduce it. Do you? Is the run button active when you modify the query, e.g. with a space somewhere?

Code modification/commit f420f2d from Ansgar Becker <anse@heidisql.com>, 2 years ago, revision 11.3.0.6388
Fix ignored cursor moves in SQL editors, broken by using OnChange instead of OnStatusChange in 38e5409dbe9758ccbd89cd858089f0728d3e4ca6. Related to #1319 and more recently reported on https://www.heidisql.com/forum.php?t=38641
BubikolRamios's profile image BubikolRamios posted 2 years ago Permalink

Unfortunately, have no proc. of reproduction ....

BubikolRamios's profile image BubikolRamios posted 2 years ago Permalink

I guess you could find where that message pops up - like "can't close tab - query running", and give user opt. to ignore that and close tab anyway.

BubikolRamios's profile image BubikolRamios posted 2 years ago Permalink

happened again: exact message: / Cannot close tab with running query. Please wait until query has finished. /

Note before sign was, there was progress mouse cursor on that guery tab, obviously all was finished cos switching to processes tab went without any prob, back to query tab = run button disabled

BubikolRamios's profile image BubikolRamios posted 2 years ago Permalink

image description

if this any help. Left comp running, was not doing anything for 2 hours. These queries take like 20 sec normally.

  1. state after 2 hours then move to host, see processes, that works normal, should not if queries would actually running, back to query --> 2, can't close query tab.
ansgar's profile image ansgar posted 2 years ago Permalink

Still cannot reproduce that here.

Could you please update to the latest build once, as I see the version of the v11.3 release in your screenshot. Just to be sure this is not yet fixed.

Please login to leave a reply, or register at first.