• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: new/update form patterns
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new/update form patterns


  • Subject: Re: new/update form patterns
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 26 May 2005 15:10:32 -0700

Doing _anything_ with an EO which has not been inserted or fetched into an EC will send EOF notifications when EOF is not expecting them. It might not bite you today, but it _will_ bite you eventually. It is not certain, immediate death, but is a bad practice and dicing with the Devil.

Chuck


On May 26, 2005, at 3:02 PM, Ondra Cada wrote:

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



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
village.net


This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers who want to increase their overall knowledge of WebObjects, or those who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects




_______________________________________________
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


References: 
 >new/update form patterns (From: Mike Schrag <email@hidden>)
 >Re: new/update form patterns (From: Ondra Cada <email@hidden>)
 >Re: new/update form patterns (From: Mike Schrag <email@hidden>)
 >Re: new/update form patterns (From: Ondra Cada <email@hidden>)

  • Prev by Date: Re: new/update form patterns
  • Next by Date: Re: new/update form patterns
  • Previous by thread: Re: new/update form patterns
  • Next by thread: Re: new/update form patterns
  • Index(es):
    • Date
    • Thread