Anthony,
If I understand you correctly you are saying that you have an FK in
some records in the source table referencing some records that do not
exist in the destination table.
If so, that's your problem. There are ways around it if you must have
the data structured this way in your da
Override awakeFromInsertion and
NSLog.out.appendln(new RuntimeException("object created"));
And see what is doing it.
Chuck
On Apr 5, 2008, at 3:50 PM, Anthony B Arthur wrote:
Yeah, that was my suspicion too, but neither of those configurations
are enabled on the owning eo's relationship.
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
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 attribu
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 thi
