I created a thread a while back regarding problems with writers blocking readers and IBReplicator http://www.nabble.com/Question-for-.NET-Provider-Author-re-transaction-conflict-to16733863.html#a16758487 here .
I am now following this up to try and bring this to a conclusion. I emailed IBReplicator again and the developer told me that in Interbase and Firebird writers don't lock readers. He said that I should add tpb_rec_version to my transaction parameters block. Or ask driver's author to do so. This is to avoid IBReplicator blocking my whole .NET app up for all other users when replication is running. I did a google on 'tpb_rec_version' but am getting absolutely nowhere with that. The previous thread seemed to be suggesting that the writer was blocking the reader. but now i am confused after the latest reply. i am really just looking for a way for my users to be not frozen out whilst IBReplicator is running. I am wondering id this tpb_rec_version is a possible solution for the .NET driver. frankly I am a bit out of my depth here so any expert opinion would be helpful. thanks. -- View this message in context: http://www.nabble.com/Writer-block-reader-issue-tp20537595p20537595.html Sent from the firebird-net-provider mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Firebird-net-provider mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
