Re: new/update form patterns
Re: new/update form patterns
- Subject: Re: new/update form patterns
- From: Ondra Cada <email@hidden>
- Date: Fri, 27 May 2005 00:02:32 +0200
Mike,
On 26.5.2005, at 22:24, Mike Schrag wrote:
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).
Far as I can say from a pretty long experience, there is no problem,
presumed you are pretty careful not to mix in relationships objects
which are in EC with those which are not. Never been bitten in my
bottom with this.
Matter of fact, a few times when needed I've even dared to create
relationships from non-EC objects to EC-ones (the inverse
relationships, of course, were set up only just before saving when
inserting the new EOs into EC), and even it did work well without
problems. That though I do not recommend for important public
applications :)
Of course, you have to be wary with whatever code might presume there
is an EC, like with using undo manager or so.
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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