distal-attribute
distal-attribute
distal-attribute
distal-attribute

3 Feature Questions

aphel posted 3 years ago in General
Let me preface by saying I really like HeidiSQL and it has a lot of strengths. There are just 3 things that I either can't seem to find options for or am hoping will be available soon:

1) Run multiple queries at a time
If you run a query the entire program locks up until it's finished. This prevents not only running other queries but continuing to gather information from other tabs (e.g. Database, Table)

2) Return the data in chunks when request is large.
The entire data set is returned at once instead of at intervals.

3) Cannot stop a query. This is mostly frustrating because of points 1 and 2.

ansgar posted 3 years ago
That sounds as if you are using the 6.0 release. If you update to the latest build you will get threaded query execution, as well as stoppable queries via button on the main toolbar.

For point 2. this is not true, at least for the data tab which always fetches 1000 rows at a time, even BLOBs are read chunkwise.
aphel posted 3 years ago
Awesome! Once the release is stable it will be amazing. As it is now, it crashes on me all the time. It especially likes to crash whenever I use the intellisense in a different query window while another query is running. It also loves to crash on me whenever I accidentally click on the "Data" tab when a query is running.


As to point 2: you're right about the "Data" tab. But if you're running a query that returns a lot of rows, all the rows are returned at once instead of at intervals. So if there are 1,000,000 rows to be returned, all 1,000,000 rows come at one time.

Point 2 probably isn't a big deal for people running localhost but it can be a drag for those remotely connecting.

ansgar posted 3 years ago
Well, it's impossible to divide a result set server-sidish into more than one chunk. Or do you have some MySQL knowledge about that?
aphel posted 3 years ago
You might have misunderstood.

If you need an example, download MySQL Query Browser, run a query that returns a lot of rows and you'll see that while the query is running, results are being displayed back to you.

HeidiSQL waits for the query to finish before returning even a single row of data.


ansgar posted 3 years ago
Then QB uses mysql_use_result() instead of mysql_store_result(), which then the effect that no further query can be fired until that SELECT has reached the last row. Years ago users and me decided not to do that in HeidiSQL, for various reasons. Well, at least in the data tab you have a similar approach with the "next" and "show all" buttons. For a custom query the user is responsible for limiting the result set.

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