Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

EOKeyValueQualifier with keypaths

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EOKeyValueQualifier with keypaths

Subject: EOKeyValueQualifier with keypaths
From: Christian Pekeler <email@hidden>
Date: Mon, 29 Nov 2004 17:27:43 -0700

Using an EOKeyValueQualifier with a keypath like toManyRelationship.attribute as argument for EOQualifier.filteredArrayWithQualifier() behaves different than using the same qualifier with a fetchSpecification against the database. Against the database I can just specify the value I'm qualifying for. Using EOQualifier.filteredArrayWithQualifier() I need to use an array of my value to get comparable results. I guess that's because valueForKeyPath() (which I presume is used by EOQualifier's implementation) returns an array of arrays for my keypath before comparing them against the value, whereas the generated sql on the database is sort of flattening the result set. That is a problem if I want to use the same qualifier in my business logic for DB operations and for in-memory filtering. I'm not sure though if this inconsistency qualifies as a bug in EOKeyValueQualifier and whether I should file a report. Any opinions or ideas for a practical workaround?

Thanks,
Christian

_______________________________________________
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



Prev by Date:
Re: Help With a Bug

Next by Date:
Re: Stupid graphics question

Previous by thread:
Re: Help With a Bug

Next by thread:
Blank Page on Deployment

Index(es):

Date
Thread