Subject | Re: [Firebird-Java] Last changes of isc_rollback_transaction |
---|---|
Author | Ann W. Harrison |
Post date | 2002-12-13T15:51:38Z |
At 10:30 AM 12/13/2002 -0500, David Jencks wrote:
the case of data conflicts in transaction processing systems. The
"reason" for rollback retaining is to allow Delphi clients to undo
work after a data conflict without losing all their context - in
Delphi, when there is no active cursor, there is no data.
Regards,
Ann
www.ibphoenix.com
We have answers.
>Hmmm, Well, the purpose of the changes to rollback were so you could callActually rollback is often used without breaking the connection, in
>rollback on the engine if there is any evidence a transaction was started,
>and to mark the transaction over no matter what happens. This is only
>required when you are making a last-ditch attempt to clean up after some
>kind of serious problem and are about to discard the connection.
the case of data conflicts in transaction processing systems. The
"reason" for rollback retaining is to allow Delphi clients to undo
work after a data conflict without losing all their context - in
Delphi, when there is no active cursor, there is no data.
Regards,
Ann
www.ibphoenix.com
We have answers.