Hi Thomas,
> I don't see deadlocks with the following test case.
Thank you very much for the test case!
> No gaps, no deadlock messages, no pk/unique violation in the log table etc ...
Same for me. Got deadlock if try with NO RECORD VERSION.
> It is crucial that accessing the central generator table is tunneled through a single access point. The SP in our case. Any chance that anything else is accessing the table in your scenario resulting in the deadlock / write update conflict?
I hope no. The user can modify the properties of the generator but just 
if the generator value is 0.
Gabor
------------------------------------
------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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-digest@yahoogroups.com 
    firebird-support-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
    firebird-support-unsubscribe@yahoogroups.com
<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/
No comments:
Post a Comment