My best suggestion is that you use @export to output the results to file and hope the restart doesn't occur before the execution in DbVisualizer has completed.
Read more in:
Not a bad work around, but I would still like to see the requested feature considered if possible. It would bypass the hassle of me adding the extra statement to each query and worrying about file management (Where did I save those results, etc). Especially since you already have a "pin" option for results and a default option to pin them (which I use). This is just taking that to the next level I guess.
We'll discuss your suggestion but spontaneously I believe it will be categorised as a low prio request.
I often have very long running queries. Last night my computer installed updates and restarted. I lost all the results that had completed after I left.
It would be nice if results tabs could reopen when DBVis is reopened.