Subject Transactions
Author Josh
Morning all

Supposing I had a bunch of queries (selects and updates) to perform a
distinct task. I might allocate all of those queries to a
TIB_Transaction and wrap the entire procedure in a try..except,
try..finally for a rollback and commit respectively.

But if I forget to allocate just one of those queries to my
TIB_Transaction, and something blows up, the transaction gets rolled
back only in part. Problem is that I don't get an error when it runs
"Expecting explicit transaction start" because the forgotten query uses
the default transaction on the IB_Connection to which it is assigned.

Is there a way to prevent the IB_Connection from creating this default
transaction, so I get the real error?



[Non-text portions of this message have been removed]