Subject | Re: Re: [IBO] Transaction->ReadOnly = true |
---|---|
Author | GOVINDKRISHNA |
Post date | 2003-10-06T07:07:42Z |
Well,
I am not an expert and would like somebody who knows more about FB to validate this.
If you are in an environment where you are opening a dataset and displaying to the user using some bound controls and the user is likely to hold this screen open for some time it is not enough if you set the transaction as a read only transaction.
If a transaction is set to read only and you open a dataset and keep it open for some time the OAT will get stuck and cause performance problems if many users are connected your database. To keep that OAT moving you will need to refresh this transaction once in a way.
However if your transaction isolation is set to read-committed then the OAT will not get stuck and you dont need to worry about refreshing your dataset.
Well I am not very sure what are the other implications of setting the transaction isolation to read-committed in your application but in my application this work fine
HTH
gk
------------------Original Message-----------
From : "gbehnke2000" <Behnke@...>
To : IBObjects@yahoogroups.com
Date : 03/10/2003 9:04:40 PM
Subject : Re: [IBO] Transaction->ReadOnly = true
Hello Helen,
many thanks for your fast response. I hope we will meet us in Fulda
for the next Firerbird Conference in 2004.
Thanks and best regards
Gerhard
I am not an expert and would like somebody who knows more about FB to validate this.
If you are in an environment where you are opening a dataset and displaying to the user using some bound controls and the user is likely to hold this screen open for some time it is not enough if you set the transaction as a read only transaction.
If a transaction is set to read only and you open a dataset and keep it open for some time the OAT will get stuck and cause performance problems if many users are connected your database. To keep that OAT moving you will need to refresh this transaction once in a way.
However if your transaction isolation is set to read-committed then the OAT will not get stuck and you dont need to worry about refreshing your dataset.
Well I am not very sure what are the other implications of setting the transaction isolation to read-committed in your application but in my application this work fine
HTH
gk
------------------Original Message-----------
From : "gbehnke2000" <Behnke@...>
To : IBObjects@yahoogroups.com
Date : 03/10/2003 9:04:40 PM
Subject : Re: [IBO] Transaction->ReadOnly = true
Hello Helen,
many thanks for your fast response. I hope we will meet us in Fulda
for the next Firerbird Conference in 2004.
Thanks and best regards
Gerhard
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> At 03:03 PM 2/10/2003 +0000, you wrote:
> >Hi all,
> >
> >i use FB 1.5 RC6.
> >In my application i set the ReadOnly Property of TIB_Transaction
> >always to true if i need only to read data's from the database.
> >I think that would increase the performance of FB. Is this true or
is
> >there no affect to do this ?
>
> It won't affect performance directly, but there is a good benefit
from
> doing this, as a read-only transaction can stay active without
inhibiting
> garbage collection.
>
> Helen
___________________________________________________________________________
IB Objects - direct, complete, custom connectivity to Firebird or InterBase
without the need for BDE, ODBC or any other layer.
___________________________________________________________________________
http://www.ibobjects.com - your IBO community resource for Tech Info papers,
keyword-searchable FAQ, community code contributions and more !
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>>>This mail is created in Hamsa. www.jlmatrix.com <<<