Re: new/update form patterns
Re: new/update form patterns
- Subject: Re: new/update form patterns
- From: Jean-François Veillette <email@hidden>
- Date: Thu, 26 May 2005 16:33:29 -0400
Le 05-05-26, à 16:24, Mike Schrag a écrit :
But most often, I am eating my cake and still having it by creating
the EO first, but saving it into EC only when properly set up. That
way, it can be wired up directly, and still, if the user abandons it,
it just vanishes when the GC decides so :)Doesn't this violate one of
the ten commandments of EOF? Isn't one of them that you're not
supposed to update an EO prior to inserting it? I've not been able
to find good docs as to WHEN that actually causes problems though
(one of our internal apps does this, too, and it seems to work fine,
but I gather it will burn us under certain circumstances).
here some point to consider :
- You have to be carefull about relationship, but for normal attributes
(String and Number) you should be ok.
- I strictly follow the rule if dealing with relationship, otherwise, I
relax a bit.
- the undo manager can't know about changes to that EO until this eo is
in the editingcontext, so be carefull as well about that. If you do
not use the undo manager, you might not have a problem.
- jfv
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden