Subject | Re: [firebird-support] rollback or commit |
---|---|
Author | Helen Borrie |
Post date | 2003-09-10T23:57:41Z |
At 05:29 PM 10/09/2003 +0100, you wrote:
default). For a read-write transaction the engine sets things up for
creating and rolling back new record versions if required. Cleaning up
after a Commit costs less than cleaning up after a Rollback.
But for a transaction set to be readonly, there is no difference.
Helen
>Daniel,It's a fact, provided the transaction read-write attribute is true (the
>
> > If not mistaken, there's no difference.
>
>If not mistaken, I think that a commit will give you less overhead that a
>rollback.
>
>But this is just a feeling. :-)
default). For a read-write transaction the engine sets things up for
creating and rolling back new record versions if required. Cleaning up
after a Commit costs less than cleaning up after a Rollback.
But for a transaction set to be readonly, there is no difference.
Helen