Re: mystery insert
Re: mystery insert
- Subject: Re: mystery insert
- From: Anthony B Arthur <email@hidden>
- Date: Sat, 5 Apr 2008 18:50:02 -0400
Yeah, that was my suspicion too, but neither of those configurations
are enabled on the owning eo's relationship.
-b
On Apr 5, 2008, at 1:48 PM, Chuck Hill wrote:
Sounds like you have turned on Propogate Primary Key (and Owns
Destination?) on a relationship after the owning object has been
created. EOF sees this and creates the mandatory owned object.
Chuck
On Apr 5, 2008, at 10:41 AM, Anthony B Arthur wrote:
Somehow, whenever I reference an attribute on an entity through a
relationship of another entity, and that relationship triggers a
fault where there is no matching record, yielding an empty
relationship, it has the side affect of inserting a new eo into
the editing context -- at least I think this is what happens. I
know for sure that in this scenario I am not explicitly creating
and inserting a new eo of this entity yet an exception is raised,
when the ec gets saved, complaining some non-nullable fields were
left blank on it. There should not be an insert or even update of
any sort on any of these entities -- anyone got a clue of what I
may be doing wrong?
--Brian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
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