> Martijn Tonies
> If you're doing a ROLLBACK while nothing has changed,
> Firebird will actually do a COMMIT instead.

Actually I am after the following issue: commit/rollback processing
strategy can be optimized for "commit expected" or, alternatively, for
"rollback expected" situations.
For "commit expected" strategy when DML occures all changes are written
directly to the tables and indexes but not marked as commited: then commit
processing has only to flag data as commited which is fast enough. Rollback
is quite slow then but rollback is really quite rear, usually one designs
transactions to commit.. Is this what Firebird does?

Regards, Laimis





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