Helen Borrie wrote:
>
> Exactly so. Writers block readers under these conditions.
>
Helen
Thanks for your reply. You have always been so helpful in the past, and I am
very grateful for that.
It is good that I have identified the reason why our software is locking.
Scheduled 'behind the scenes' replication is very much a feature I would
like to keep. Yet at the same time it is unacceptable for our software to
lock each time this happens.
I am unsure of what my options are here. Should I consider changing the
isolation level for our transactions? Will this only create different
problems?
Your advice would be much appreciated. Many thanks.
--
View this message in context:
http://www.nabble.com/Question-for-.NET-Provider-Author-re-transaction-conflict-tp16733863p16758487.html
Sent from the firebird-net-provider mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
