Subject | Re: [firebird-support] Re: Help Firebird Crashing every day |
---|---|
Author | Carlos H. Cantu |
Post date | 2010-04-23T14:22Z |
z> I had problems with this in the past.
z> If i start reading data using IsolationLevel.ReadCommitted on a
z> time consuming query, and table gets heavily updated in meantime,
z> data reading gets stucked until updating is done.
Hummm... it should not happen if you use RecVersion parameter.
z> This is desirable behavior for issuing flight tickets, but for
z> showing sport results or showing reports it's a problem.
z> If i specify IsolationLevel.RepeatableRead there is no problem.
z> Check this out:
z> http://firebird.1100200.n4.nabble.com/Writer-block-reader-issue-td1106813.html
z> Truth to be said, it was quite while ago, and i'm not sure that
z> IsolationLevel.ReadCommitted internals have changed.
I always used readcommited + NO WAIT + RecVersion in my browsing/data
editing forms, and never had problems of server getting stuck. I use
snapshot for reports and some tasks where I need stable view of the
data. BTW, I use IBO (not the .net provider).
[]s
Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org - www.FireBase.com.br
z> --- In firebird-support@yahoogroups.com, "Carlos H. Cantu" <listas@...> wrote:
z> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
z> Visit http://www.firebirdsql.org and click the Resources item
z> on the main (top) menu. Try Knowledgebase and FAQ links !
z> Also search the knowledgebases at http://www.ibphoenix.com
z> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
z> Yahoo! Groups Links
z> If i start reading data using IsolationLevel.ReadCommitted on a
z> time consuming query, and table gets heavily updated in meantime,
z> data reading gets stucked until updating is done.
Hummm... it should not happen if you use RecVersion parameter.
z> This is desirable behavior for issuing flight tickets, but for
z> showing sport results or showing reports it's a problem.
z> If i specify IsolationLevel.RepeatableRead there is no problem.
z> Check this out:
z> http://firebird.1100200.n4.nabble.com/Writer-block-reader-issue-td1106813.html
z> Truth to be said, it was quite while ago, and i'm not sure that
z> IsolationLevel.ReadCommitted internals have changed.
I always used readcommited + NO WAIT + RecVersion in my browsing/data
editing forms, and never had problems of server getting stuck. I use
snapshot for reports and some tasks where I need stable view of the
data. BTW, I use IBO (not the .net provider).
[]s
Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org - www.FireBase.com.br
z> --- In firebird-support@yahoogroups.com, "Carlos H. Cantu" <listas@...> wrote:
>>z> ------------------------------------
>> z> 3. If your database is updated a lot, and you use default .net
>> z> transaction (IsolationLevel.ReadCommitted) while reading data,
>> z> WRITERS BLOCK READERS.
>>
>> A ReadCommited transaction can see commited records by transactions
>> that were started after the ReadCommited one. It is not true that
>> writers block readers.
>>
>> Carlos
>> Firebird Performance in Detail - http://videos.firebirddevelopersday.com
>> www.firebirdnews.org - www.FireBase.com.br
>>
z> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
z> Visit http://www.firebirdsql.org and click the Resources item
z> on the main (top) menu. Try Knowledgebase and FAQ links !
z> Also search the knowledgebases at http://www.ibphoenix.com
z> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
z> Yahoo! Groups Links