Re: Null values at end of sorted list
Re: Null values at end of sorted list
- Subject: Re: Null values at end of sorted list
- From: Lachlan Deck <email@hidden>
- Date: Sat, 2 Feb 2008 17:31:15 +1100
Hi Aaron,
On 02/02/2008, at 8:35 AM, email@hidden wrote:
I'm not sure what your code was fixing though. I thought that
"Object.class" was the root of everything and would be a catch all.
Actually, yes my bad. I scanned the code too quickly.
So is your code even getting called during fetches from the db?
Alternative... subclass EODatabaseContext (e.g., overriding
objectsWithFetchSpecification( EOFetchSpecification fetchSpec,
EOEditingContext context ). This is what I'm doing for ensuring a
default sort for certain entities prior to calling super. Some
alternative to that might work, or delegate method. At least you
might be able to trace what's getting called.
Have you also looked at EOQualifier.Comparison[Support]? It talks a
little about Java Client, however these might have a part to play in
normal server-side stuff anyway.
with regards,
--
Lachlan Deck
_______________________________________________
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