Check Connection and results

[ScottMattes]

OK, I had a Test Window where I had just run a test that updated data. The Commit/Rollback buttons were enabled and since there was stuff that I wanted to check before doing either I went off to lunch. When I got back about 30 min later I poked around a bit and then clicked the rollback button and was told that I wasn't connected. So, I clicked the execute (not execute with debug) and it ran just fine.

So, how come one says that I am not connected and the other acts like it is connected?

 

[Marco Kalter]

The commit/rollback buttons will try to commit/rollback the transaction of the current session. If the session is somehow lost, this will raise an exception.

Executing the Test Script will first check if the current session is alive and will establish a new session if this is not the case.

 

[ScottMattes]

Does that mean that in Preferences, Check Connection does not keep the session 'alive' (so that the DB is fooled into believing that I am still active)?

 

[Marco Kalter]

The Check Connection option does prevent a session from timing out. But if there the session is killed for another reason than timing out, it cannot prevent this issue.