Restore tabs on crash

Hi,

sometimes, HeidiSQL may be stuck or may end to crash. In such case, the unsaved tabs are lost.

It would be great to have a way to keep the tabs content, like Notepad++ does (it keeps the unsaved files on close or crash and restore them on reopening). That could be done by saving all tabs (on change or periodically) in temporary files, and restore them when opening HeidiSQL. When closing a tab, the temporary file would be removed.

Such a feature would be most welcome, since Windows 10 nowdays restarts the machine without thinking twice when installing updates.

I'd really like that too!

+1

I totally agree: This is THE MOST WANTED FEATURE on my list!!!

Actually, the absense of this feature (combined with HeidiSQL`s tendency to crash on lost connections) is the only reason why I stopped using HeidiSQL for important work. I would immediately return to using HeidiSQL as soon as this feature is implemented, as then those crashes would not be such a problem anymore!

+1

If you have sessions with all open tabs/files may be a good approach to that issue.

I just learned the hard way that I want this feature; 4 hours of work lost due to a crash in combination with my own stupidity of not saving the file regularly. This is undoubtedly my most wanted feature now!

Well, the last release v10.2 already has this feature. You should probably activate Tools > Preferences > "Check for updates" ;)

Well, the last release v10.2 already has this feature. You should probably activate Tools > Preferences > "Check for updates" ;)

Thanks for the tip, I have now checked the "Check for updates" setting, with [day] set to 1 (every day, right? Or should I use 0?). However, I'm already on 10.2.0.5599 and the work I had done in the tab was gone.

Does the feature also apply to unexpected crashes (both in HeidiSQL and full blown computer crashes)?

It could also be noteworthy that I am working with multiple instances of HeidiSQL at a time (one for a production session and one for a local testing environment), how does this impact the tab restoring feature? Does it save both instances separately, both in one place, does the "last session" overwrite the "first one(s)" or does it ignore saving the tabs? When restoring, would I get the different tabs in the correct sessions, or all tabs in the first session?

Thanks for any input!

Does the feature also apply to unexpected crashes (both in HeidiSQL and full blown computer crashes)?

Tabs are stored each 10 seconds, so yes - that should help in both cases.

About multiple application instances: that's of course taken care of. But do not expect wonders - I have seen rare error messages saying that the global tabs.ini file was locked and could not be written to, although HeidiSQL releases the file handle after saving and reading. In any normal case, if it's currently locked for some seconds by some other process, HeidiSQL keeps on trying to write, up to 3 seconds long. For me that works perfectly in the last builds. And it's very conveniant not to have to be asked to store them manually each time I exit HeidiSQL.

Please note that you should update to the latest build at least once, as I fixed some minor tab-restoration things after the last v10.2 release. You can update to a nightly build through Help > Check for updates.

Hi I realise this an old post;

I am getting a MySql authentication error at the minute - so I can't access the "unsaved" tabs. Are these stored in a file somewhere that I can get access to?

Thanks!

Sorry for the post - I managed to find them after a little while. Windows 11; C:\Users\gavin\AppData\Roaming\HeidiSQL\Backups