Comments on: Recovering from optimistic locking exceptions http://terminalapp.net/recovering-from-optimistic-locking-exceptions/ All computers should be destroyed. And flies too. Thu, 28 Aug 2008 12:43:37 +0000 http://wordpress.org/?v=2.5 By: Miguel Arroz http://terminalapp.net/recovering-from-optimistic-locking-exceptions/#comment-70 Miguel Arroz Mon, 20 Aug 2007 18:19:19 +0000 http://terminalapp.net/recovering-from-optimistic-locking-exceptions/#comment-70 Typo fixed! Thanks! :) Typo fixed! Thanks! :)

]]> By: Paulo Andrade http://terminalapp.net/recovering-from-optimistic-locking-exceptions/#comment-69 Paulo Andrade Mon, 20 Aug 2007 17:25:47 +0000 http://terminalapp.net/recovering-from-optimistic-locking-exceptions/#comment-69 I know you have been told this before, but you sure know how to have fun with WO. Just a couple of remarks: 1 - As you said in your comments the "NoMerging" delegate isn't really needed. This is because your are registering your context with the lockManager, and while the context is locked no merging occurs. 2 - With that cleared out, there's a typo in the last paragraph. Fetching objects from the store and causing a performance hit is not an advantage :P. I know you have been told this before, but you sure know how to have fun with WO.
Just a couple of remarks:
1 - As you said in your comments the “NoMerging” delegate isn’t really needed. This is because your are registering your context with the lockManager, and while the context is locked no merging occurs.

2 - With that cleared out, there’s a typo in the last paragraph. Fetching objects from the store and causing a performance hit is not an advantage :P.

]]>