Using 184.108.40.2060, I just accidentally noticed that a DBISQL session had been re-established after a short network problem. (I was not even aware that DBISQL can do that...)
The server log shows the typical "Dropped client connection entry" but DBISQL has not presented a visual sign of the re-connect to me. (If it has shown a message temporarily, well, I was not sitting in front of the machine during the re-connect. - And no, I was no causing the network problem, either:))
I'm asking because I noticed the re-connect simply because a connection variable that had been used before was no longer valid when I ran the next statement, and thereby leading to a different behaviour - in my case an error message but otherwise somesting unexpected could have taken place, as well.
An automatic re-connect may be a helpful feature, but when the re-established connection does not inherit all properties of the original one (because that may be not possible, I'd think, and at least it has a different connection number), a warning should be issued.
BTW: Is that re-connection feature documented?