[seam-dev] To cascade or not...

Dan Allen dan.j.allen at gmail.com
Wed Mar 4 14:34:27 EST 2009


On Wed, Mar 4, 2009 at 2:12 PM, Daniel Hinojosa <dhinojosa at evolutionnext.com
> wrote:

> 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.


Thanks for reminding me of the DELETE use case Dan. No question that is the
most important one, even more than PERSIST.

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

PERSIST, DELETE, REFRESH

-Dan

-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20090304/64698947/attachment.html 


More information about the seam-dev mailing list