29.04.2016 12:38, Gabor Boros wrote: >> This is true for two concurrent transactions but may fail for three or >> more concurrent transactions. > > Your words shocked me. Firebird cannot handle more than two concurrent > transactions? What is the purpose of WITH LOCK if see deadlock with and > without it?
Apparently, I was wrong. My statement is correct for updates inside no-record-version + wait transactions, but WITH LOCK is implemented in a more clever way and works around this issue by refetching the last committed version and posting its dummy update on top. So update conflicts should not be possible there. Did you see the same issue on v2.5 or only on v3.0? Maybe it's a regression introduced in the new version. I'm checking the code now, will report back if anything useful is found. Dmitry ------------------------------------ ------------------------------------ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ------------------------------------ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: firebird-support-dig...@yahoogroups.com firebird-support-fullfeatu...@yahoogroups.com <*> To unsubscribe from this group, send an email to: firebird-support-unsubscr...@yahoogroups.com <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
