Re: EOObjectNotAvailableException
Re: EOObjectNotAvailableException
- Subject: Re: EOObjectNotAvailableException
- From: Ken Anderson <email@hidden>
- Date: Thu, 27 Jul 2006 10:10:23 -0400
Anjo,
Unfortunately, that's not always possible. On my last big project,
EOF came long after the database schema was defined and in-use. It's
not uncommon for there to be a primary row, with multiple optional
rows, all with the same primary key. This was considered normal and
acceptable before unique integer primary keys were being used. So,
to paraphrase, I understand Garry's pain :)
Ken
On Jul 27, 2006, at 1:11 AM, Anjo Krank wrote:
Am 25.07.2006 um 17:20 schrieb Watkins, Garry:
Really not the answer that I wanted. Personally, I think that it
is a
bug in EO, if the relationship is defined as NOT mandatory, and it
encounters a EOObjectNotAvailableException it should return null.
However, I want to continue to use EOGenericRecords since it is
mainly a
reporting type application. Does anyone know where the Fault is
triggered inside the EO stack so that I might be able to trap the
operation with AspectJ? This would also require that I have the
EORelationship that triggered the fault.
If you have a key that points into nirvana, your data is broken and
should be fixed. EOF certainly should *not* return null in this case.
You could probably write an accessor to your relationship and trap
the exception there or get the committed snapshot in the EODBC or
EODB and patch it to be null. But the easiest route is to fix your
data.
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anderhome.com
This email sent to email@hidden
_______________________________________________
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