Autosave work in progress to prevent headaches during app crashes.

[expired user #8393]'s profile image [expired user #8393] posted 9 years ago in Feature discussion Permalink
Hi,

Software crashing, or, with regards to Windows, automatic reboots due to Windows Updates even though the machine is in hibernated and powered down, are a fact of life.

The issue is that the queries I've been building up are lost.

Sometimes there are fairly significant works.

It would be nice to have an automatic cache of all queries as they are typed and/or before execution.

Not to named files, just cache the queries where they can be retrieved if there is a crash.

Like I have right now.

9 tabs of queries. Several hours of work to do the analysis. And now Heidi is "Not Responding"... <bang> <bang> <bang> <bang> <bang> <bang> (sound of head hitting desk).

As a user of PHPStorm (for example), as I type, the file is saved. Almost character by character. I don't think I ever actually use "Save".

Admittedly PHPStorm saves to a named file, but for HeidiSQL, it could easily use a structured file to store the query tabs contents. Doesn't need to be human readable really, but XML (I like XML) is going to be easy enough.

Regards,

Richard Quadling.
[expired user #8737]'s profile image [expired user #8737] posted 9 years ago Permalink
Yes, the tabs should be saved as you type so that a crash will restore your work to where you left off. I often have 30+ queries in my tabs because of size and diversity of our application and the tables and queries I need for development and support.

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