I've been pondering what the ramifications to sql session disconnects are. I have seen in other "professionally developed" applications, like our accounting software used here, that if the user gets disconnected for anything longer than a few seconds, the software completely bails out through a series of errors that I have to abort to get the app to quit. Not very graceful. I want to make my software more robust.
So I am wondering what happens when there is a transaction in effect, and there is an unexpected disconnect. Will reconnecting restore the transaction state or is it flushed after the sql timeout? If I can reconnect and the transaction is still in effect, well and good, but if I proceed as though the transaction is still in effect and it is not, bad things could conceivably happen. Is completely bailing out the best approach after all? Bob _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
