Saving Queries
| User, date | Message |
|---|---|
|
Written by djdjohnson
2 years ago Category: Feature discussion 59 posts since Mon, 28 Jun 10 |
I love HeidiSQL, but it just isn't stable. It crashes and locks up on me all of the time. Ultimately, it would be great if it never crashed, but I don't see that happening any time soon. Until that can happen, I lose a lot of complicated queries because I don't take the time to save every query before I run it. I know, shame on me for not saving every query before I run it, but this would take a lot of time. I run hundreds of queries per day. What would be really nice would be if HeidiSQL were to save all open queries (to disk, in the registry, whatever) before they're executed just in case it locks up or crashes during execution. When it completes execution, it can delete those saved queries. If it does happen to lockup or crash during query execution, it would see those in the registry the next time it loads and automatically restore the contents of those Query tabs so they aren't lost forever. These queries would obviously have to be saved per-connection (as they probably wouldn't make sense on other servers), and include other state information like which database is currently selected. |
|
Written by muzza4
2 years ago 50 posts since Mon, 04 Dec 06 |
Just in case anyone thinks this is one off, I have the same issues with the stability. My problem isn't so much losing queries (though I do) but when I need to find something in the database HeidiSQL immediately crashes on me and by the time I've reopened it I've lost focus on the issue I am dealing with. Some of the new features are great, but in my view it's the stability that needs the development effort. Regards Muzza |
|
Written by ansgar
2 years ago 3950 posts since Fri, 07 Apr 06 |
Be aware you're talking about the latest builds which can of course contain incomplete and non-bugfree stuff. Also, have a look at issue #2331 and feel free to comment there. |
|
Written by djdjohnson
2 years ago 59 posts since Mon, 28 Jun 10 |
While that issue is similar, I'm not looking to save queries between sessions. Just be able to get them back when the app crashes or locks up. |
|
Written by ansgar
2 years ago 3950 posts since Fri, 07 Apr 06 |
Well probably I can do that in the same report. But I prefer fixing the crashes instead of tinkering the effects. |
|
Written by simbabque
1 year ago 5 posts since Tue, 11 Jan 11 |
That happens to me sometimes. In these cases I just look up the query in the connection log file. Remember that you have to turn it on because it starts out without logging. But if there is a log file than there's a very good chance to get the twenty unsaved queries you fried with your heavy one back by just taking a look there. |
|
Written by djdjohnson
1 year ago 59 posts since Mon, 28 Jun 10 |
FWIW, I'm still losing queries when HeidiSQL locks up (which, unfortunately, happens many times a day). A quick save of queries to the registry (in the key associated with the current connection), and deleting them when the query results are retrieved would take care of this. If HeidiSQL opens with query data in the registry, it restores the queries automatically. |
|
Written by Kevin
11 months ago 1 posts since Fri, 29 Jun 12 |
Hello, I would also like to see a "Restore Queries on Crash" feture soon. My HeidiSQL crashes several times a day - but no software will ever be 100% bug free, anyway. Toad offers this crash recovery feature (yes, it also crashes  and due to the frequency of crashes I am considering to move to Toad...Regards Kevin |
|
Please login to leave a reply, or register at first. |