| Subject | Isolating a transaction with a TIBODatabase |
|---|---|
| Author | Ed Dressel |
| Post date | 2011-08-23T20:15:47Z |
IBO 4.9.9
I run SQL statements with TIB_Cursor & TIB_DSQL objects that I create and free on the fly. They use the TIBODatabase for their connection and the default transaction associated with the TIBODatabase. When I run the SQL, the changes are visible to other TIBODatabase objects.
I checked the DefaultTransaction settings and set AutoCommit to false, but this did not fix it.
How can I keep the transactions from committing until I explicitly tell it to?
Thank you,
Ed Dressel
I run SQL statements with TIB_Cursor & TIB_DSQL objects that I create and free on the fly. They use the TIBODatabase for their connection and the default transaction associated with the TIBODatabase. When I run the SQL, the changes are visible to other TIBODatabase objects.
I checked the DefaultTransaction settings and set AutoCommit to false, but this did not fix it.
How can I keep the transactions from committing until I explicitly tell it to?
Thank you,
Ed Dressel