Re: Modeling an optional to-one relationship
Re: Modeling an optional to-one relationship
- Subject: Re: Modeling an optional to-one relationship
- From: Mark Ritchie <email@hidden>
- Date: Thu, 14 Jan 2010 03:36:28 -0800
Hi Chuck!
On 13/Jan/2010, at 5:17 PM, Chuck Hill wrote:
> The Obj-C implementation is hazy in my memory. In Java, rather than throwing a hissy fit, it will create a "dummy fault EO". That is, an EO with all null values and no real existence. What Lon wants is a real null, not a dummy EO. Kelly Hawk's fix was to throw an exception (the old behavior) rather than return some insane zombie EO. That fix (thanks Kelly!) is still in my Java code and I think lurking in Wonder somewhere too.
Yes, I believe that's the intended behaviour... The DatabaseContext tracks that newly created EO and throws an exception if you attempt to modify and then save it.
A search of my Wonder workarea which I'd just sync'd revealed only one reference to the code:
./Common/Frameworks/ERExtensions/Documentation/ReleaseNotes.txt:ERDatabaseContextDelegate - Added Kelly Hawks' fix for the missing to one relationship
I could not find any of the actual implementation anymore.
If you had a Java version, perhaps you could dig it up?
Thanks!
Mark
_______________________________________________
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