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 database but if you are in
control of the schema then don't write it that way. If not then we
can discuss workarounds.
-Dave
On Apr 5, 2008, at 1:41 PM, 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 (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/dfe%40tgwbd.org
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
