Subject | RE: [IBO] Questions about transactions and generators |
---|---|
Author | Jason Wharton |
Post date | 2004-05-22T13:10:59Z |
Minor correction to this statement:
"CancelAll cancels any work pending in your datasets that has not yet been
posted. It won't
work in an AutoCommit transaction."
CancelAll has no regard for the AutoCommit setting. If any dataset is in an
edit state for the transaction then calling CancelAll will simply cancel the
edit state. When doing a Rollback it first calls CancelAll prior to sending
the command to the server telling it to rollback any changes that have
already been posted.
I think what Helen was trying to point out is that there is no difference
between CancelAll and Rollback if you are in AutoCommit mode. This is simply
due to the fact that anything posted will be committed so there is nothing
to rollback.
Jason Wharton
www.ibobjects.com
"CancelAll cancels any work pending in your datasets that has not yet been
posted. It won't
work in an AutoCommit transaction."
CancelAll has no regard for the AutoCommit setting. If any dataset is in an
edit state for the transaction then calling CancelAll will simply cancel the
edit state. When doing a Rollback it first calls CancelAll prior to sending
the command to the server telling it to rollback any changes that have
already been posted.
I think what Helen was trying to point out is that there is no difference
between CancelAll and Rollback if you are in AutoCommit mode. This is simply
due to the fact that anything posted will be committed so there is nothing
to rollback.
Jason Wharton
www.ibobjects.com