<div class="gmail_quote">On Wed, Mar 4, 2009 at 2:12 PM, Daniel Hinojosa <span dir="ltr"><<a href="mailto:dhinojosa@evolutionnext.com">dhinojosa@evolutionnext.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If I am put my 5 cents (inflation). My personal default is (PERSIST, MERGE, REFRESH) and in the circumstance that I need to put a DELETE then I would if necessary. I assume beginner Seam developers would absolutely freak if they saw a detached entity exceptions when they first use Seam's reveng.</blockquote>
<div><br>Thanks for reminding me of the DELETE use case Dan. No question that is the most important one, even more than PERSIST.<br><br>I pretend that MERGE doesn't exist because I personally I detest it. REFRESH makes sense, though few new comers would run into it. Perhaps we can go with<br>
<br>PERSIST, DELETE, REFRESH<br><br>-Dan</div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>from my email. If you contact me, but don't hear back for more than a week,<br>
it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>you feel that it did not reach my attention.<br>