Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

Program freeze when it tries to fetch colum names while another query is running

halvor07's profile image halvor07 posted 6 years ago in General Permalink

When I run queries that takes a long time I like to begin writing the next query before the previous one is done.

Normally, when writing e.g. "SELECT my_table." you get a list of columns in that table to make it easier to find the correct one. This is very helpful, but if a query is already running when writing this, the program freeze until the first query is done. I guess this is because it only have one connection and have to wait in line to run the query for the autocomplete.

To un-freeze, you either have to wait for the first query to finish, or kill the first query from another instance or console. When killing the query, HeidiSQL resumes and just gives you an error message. If you wait for the query to finish, it either resumes as normal, gives you an error message or crash. I have not been able to determine what decides what happens, but it may have something to do with how long the query runs.

Not sure how hard this is to fix, but I would be satisfied if the program just didn't try to fetch column names while another query is running.

ansgar's profile image ansgar posted 6 years ago Permalink

Confirmed. At least writing on some SQL query should not be interrupted by non-important queries which have to wait for the running query to finish.

xmedeko's profile image xmedeko posted 5 years ago Permalink

See the GitHub issue: https://github.com/HeidiSQL/HeidiSQL/issues/10

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




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.