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

Suggestion from first time user

samurai posted 2 years ago in Feature discussion
First time I tried HeidiSQL today and I'm loving it. Thank for making it! It's light-weight yet feature rich. I have two suggestion to make it even better.

- Import progress bar (possible?)
I was trying to import a CSV with >1.5 million rows (Win7/P4/1.5GB ram) I have no idea when or if it will finish still waiting after half hour. My PC: Win7/Pentium 4/1.5GB ram
I think even an estimation taking into account the system resources and import file size would be good enough.

- Refresh table list automatically after query is run.

That's all for now. :)
samurai posted 2 years ago
Actually it was >10million rows and it just finished after about 45min or so. :)
samurai posted 2 years ago
I was thinking of a different table in my original post.
samurai posted 2 years ago
Please ignore the second suggestion I found the autorefresh option.
ansgar posted 2 years ago
With regard to yout import progess question: Was it the "Run SQL file" dialog, or did you load that file into the query editor?

The "Run SQL file" dialog already has a progress bar. Additionally, I should make the Windows taskbar button show the progress. That way, you see progress even when the dialog is busy, as this runs queries in the main application thread.

samurai posted 2 years ago
I used the "Import CSV file" feature, haven't used the other import methods. Your taskbar idea would be very handy as well.
ansgar posted 2 years ago
Ok, the CSV import makes use of MySQL's LOAD DATA command, which is just one command in the end, without the possibility to get some progress information inbetween. But the second parse method ("Client parses file contents") does that in HeidiSQL itself, and there is some loop logic which lets me display the progress in some way.
samurai posted 2 years ago
I wonder which is the faster method. I guess LOAD DATA sense you have set that as default.
ansgar posted 2 years ago
Yes, I also think so. HeidiSQL just passes the filename along with a LOAD DATA command to the server, and I guess a) the server's implementation for that is faster than HeidiSQL's CSV parsing. Also, b) the server has in most cases faster CPUs and RAM. Finally, c), and this is the most significant difference - HeidiSQL's "Client parser" needs to transport all data over the network, even produces multiple queries, each of them has some overhead.

But this is all not really important if your MySQL user does not have the privilege to run a LOAD DATA command. I have implemented the client parser for exactly such cases.

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