Re: new/update form patterns
Re: new/update form patterns
- Subject: Re: new/update form patterns
- From: Mike Schrag <email@hidden>
- Date: Thu, 26 May 2005 16:24:09 -0400
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). |
_______________________________________________
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