when crash, restored unsaved open query tabs

[expired user #9515]'s profile image [expired user #9515] posted 8 years ago in Feature discussion Permalink

I get a few crashes here and there from HeidiSQL, to not loose the code I had written, would it be possilbe to save all the open Query Tabs somehow/or at least unsaved queries? So, that once I open HeidiSQL again, the unsaved query Tabs would be restored to the state when HeidiSQL crashed.

I know of this functionality from Notepad++, when it crashes or the user just closes the gui window, all the open unsaved files are restored.

[expired user #9548]'s profile image [expired user #9548] posted 8 years ago Permalink

This is one of the first feature I look for with all editor/IDE/etc.

Personal anecdotal story: stayed a bit later last night, opened 3 sessions to the same server (actually, I only wanted 3 windows, but I think HeidSQL open another instance when doing this, I'm a new user), put some queries there and there and some comments, so this morning I would kick in fast. Windows 10 decided to restart. Yep, I disabled auto-update, but I am learning to use it and it looks like it auto-scheduled the update (I did not confirm just ignored I think)... and rebooted... and therefore closed everything. Fortunately, most of my tools auto-save-buffer/restore (Chrome, Sublime for my text notes, Explorer Folders, etc.).

I am always surprised those kind of safety features are often "optional" or you need to enable them explicitly. I might have to give some thoughts, but at first glance, they should be on by default. Anyone who want to share a different opinion with justifications against it being a default? I can maybe think of a kind of privacy/security/similar reason where an user closing an app does not expect the apps to remember "his things" (opened page, text buffer, etc.) so that can be seen as a kind of security/privacy problem. At the same time, losing your data hurts and can hurts a lot. ;-) But I can buy the you close, everything flush out idea to justify a default that does not remember everything. However, I expect/hope for a workspace/session manager in all my tools (especially dev, but not limited). Even if better not, my apps crashing, I can live with it, especially if everything come back as before. My apps crashing, closing, whatever, but losing everything, I can live with it too, because I have no choice... but I get sad :'( and I prefer to be happy happy! :)

Probably there is an option in HeidiSQL for this already, but if not, I will of course be a strong advocat for it! ;-)

I stumbled on a old discussion about how should HeidSQL restore a session where there was some disagreement about restoring the full workspace or not (with database, opened table tree, etc.). Ideally it restores everything when you close and reopen (when the option is enabled). In practice, of course, if the database and table schema change, you won't be able to restore everything as it was (unless you restore everything as it was shown when session was closed, but offer to refresh if you detect something changed, or just like if I let the editor open and someone else change something, my view will be desync, so it should behave the same, like give me error "column not existing" if someone erase one, etc.).

In my case here, I opened 3 windows to the same server just because I wanted 3 query windows to view them all at the same time (I did not look if there was a better way to do it in HeidiSQL). But I just tried to see if I can "Exit" all windows at once and it seems like each windows is an independent process which there is pro and con.

My preference would probably be like a kind of windows/tabs session (think Chrome, Sublime to give good examples, Chrome being slightly above in term of smoothness and tabs possibilities, like multiple selection of tabs at once and be able to move a selection elsewhere, etc.). I think mostly for Query Tabs for now... but it should probably be applicable to any things in the workspace.

So is there an option allowing me to manage it that way?
(talking to the author if he see this) Are you open and attracted to this? Do you see this as an hard to implement feature? Etc.

I can participate and give constructive feedbacks/ideas if need to (here I just shoot you my feedbacks fast, but I will of course think deeper/better if it can help to make things better for everyone).

Thanks

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