Subject Re: [firebird-support] read-only select generates 'lock conflict on no wait transaction'?
Author Carlos H. Cantu
Post date 2014-09-18T17:50:10Z
Re: [firebird-support] read-only select generates 'lock conflict on no wait transaction'? Afair, the only way to get lock conflict with a select using readcommited transactions is if you set the RecVersion to false, NoWait,  and the select find some record with active versions (ie: uncommited records from other transactions).

[]s
Carlos
Firebird Performance in Detail - http://videos.firebirddevelopersday.com
www.firebirdnews.org - www.FireBase.com.br


thanks for the quick reply

i'll create another IBOTransaction and use it for the one query that is doing the 'read-only' simple select that is resulting in the error.

would you expect that error to occur every time a 2nd user does a readonly select that includes the 1st users record in edit mode?

the users do not see that error every time.  just once in a while.