SqlDbx
You are not logged in.
Pages: 1
Please consider auto-saving the current session state periodically (if anything changed in the editor).
Sqldbx is quite robust... still I managed to crash sqldbx (trying to ungroup the grid, not sure exactly what I did), and obviously sqldbx reverted to yesterday's session state.
(I know I can save state manually, it's just that I forget...)
Offline
I thought we do not need it because we never crash,
but looks like it's not as crash proof as we thought
Offline
I can really appreciate a good crash from time to time but it's the re-typing that annoys me :-)
Come to think of it, I'm not worried about power cuts, so there's no need for timed auto-save--I'd be very happy if you could just catch any remaining exception at the topmost level, and save the session (quietly without user interaction) before exiting.
Offline
Pages: 1