--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> At 11:02 PM 26/02/2004 +0000, you wrote:
> >I read the FIBPlus reveiew in Delphi Informant review by Bill Tod
> >that IB7.1 no longer has problems with long running transactions.

Is

> >this an issue with Firebird 1.5?
>
> Bill said:
> "Using separate transactions for reading and updating the data lets

you

> commit changes without having the dataset closed. This works

particularly

> well with InterBase 7.1, because you can make the read transaction
> read-committed and read-only - and that means the transaction can

stay open

> forever with no impact on performance."
>
> He gives the impression that this is true only with InterBase 7.1.

In

> fact, it's true with all versions of InterBase and Firebird. It's a

factor

> of the multi-generational architecture, not some "new feature" in IB

7.1. :-)

Helen, dryasdust's precise definition: this feature (read-only
read_commited transactions started in "commited" state) was not used
in InterBase before 6.5. One more dryasdust's precise definition: in
Firebird it was introduced by Ann before InterBase ;) IMO Bill speaks
here mainly about IBX's architecture fault - in TIBDataSet all
modifying ...SQL subcomponets run in the same transaction with
SelectSQL one, so this transaction can't be made read only. FIBPlus
long ago allowed to use different transactions for mentioned
subcomponets so SelectSQL can be made read-only.

Best regards,
Alexander.