Description:
When working on a server with non-trivial structure it is a pain to find your way back to the object I was working one last time I had WB open. Also setting up all the scripts I had open, essentially the entire state in which WQE was when I left it is time consuming and annyoing. Hence what I would like to have is that WQE stores its state (per connection) so I can easily go back to my work envrionment where I left it at any time.
This feature should be optional (not everyone might need/want that) and it should be clever enough to deal intelligently with problematic data (e.g. such that would take a long time to run or consume huge amounts of memory). Don't restore blindly but also don't just ignore such data.
How to repeat:
Go into WQE, possibly with a server that has many schemata. Open A table and a number of scripts. Change the split position so you get a large result set area. Pin a few results, then close WB and reopen it. It will take you quite some time to restore your settings.
Suggested fix:
Implement persistent sessions, so we can return to them when we want to. This could also be extended to be a list of states we can choose from, depending on the work we have to do, similar to snapshots (only without the data, just the state).
