In memory qualification issues
In memory qualification issues
- Subject: In memory qualification issues
- From: Ken Anderson <email@hidden>
- Date: Wed, 21 Dec 2005 17:09:46 -0500
List Colleagues,
I've had a couple of experiences lately with in-memory qualification
and EOKeyValueQualifier that I need to bounce off the list to make
sure I'm not losing it. I've had 2 recent issues:
1. BigDecimal equality is not handled properly. Even if the objects
are initialized from strings or database fields with proper
resolution (ie not from floats!), EOKeyValueQualifier is not able to
determine proper equality. The way I made this work was to subclass
EOKeyValueQualifier, override evaluateWithObject(), check if the
objects are BigDecimals, and do a compareTo() instead of equals().
2. In Objective-C, I never had a problem with object equality for
relationships. If the 2 objects have the same Global ID, but are
from 2 different contexts, EOKeyValueQualifier now no longer sees
them as equal as it should. The way I've fixed this is to check for
EOs in the comparison, and compare their global IDs instead.
It seems from the documentation that you can override comparison
support, but I can't seem to find out how. Any pointers? Anyone
have similar experiences?
Thanks,
Ken
_______________________________________________
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