Hi,

At January 13, 2004, 12:31, lnd@... wrote:

>> 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?

You might want to read these documents:
http://www.ibphoenix.com/main.nfs?a=ibphoenix&l=;IBPHOENIX.KNOWLEDGEBASE;ID='128'
http://www.ibphoenix.com/main.nfs?a=ibphoenix&l=;IBPHOENIX.PAGES;NAME='ibp_oit'

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)