On Dec 17, 2008, at 8:16 AM, David Avendasora wrote:
Hi all,
Before I start: yes Chuck, I've googled, searched documentation, etc
aboot this. :-P
I have a to-one relationship in which the destination object may or
may not actually exist. The destination object may get deleted out
of the database without EOF's knowledge. The FK values are still in
the original table, but the record in the destination table is gone.
The destination table is in a Microsoft (Great Plains) Dynamics
database.
This causes an ObjectNotAvailableException to be thown. What I'd
like the relationship to return is null.
Isn't this what an Outer Join is supposed to do?
Kinda, sorta, but that is not going to help here.
See public boolean
databaseContextFailedToFetchObject(EODatabaseContext context, Object
object, EOGlobalID gid)
in ERXDatabaseContextDelegate for a sort of solution. It does not set
the relationship to null (though that might be possible), but it does
give you a null valued EO.
The problem is that I can't select Outer Join for the relationship
in Entity Modeler. The drop-down is grayed-out.
1) Is this the correct use of an Outer Join
Pre-coffee Chuck says no.
2) Why can't I set it?
Try deleting and re-creating the relationship.
Chuck
--
Chuck Hill Senior Consultant / VP Development
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
