Do you need to escape the equals and quotes on the qualifier?
On 23 Jul 2011 17:18, "Elizabeth Lynch" <[email protected]> wrote:
> My ERREST application has progressed nicely, feeding an iPhone app, and I
have a couple more very similar projects to work on over summer.
>
> However, I am experiencing a problem with my baseQualifier not being
applied. Code sample:
>
> public class CategoryController extends ERXRouteController {
> ...
> public static EOQualifier baseQualifier() {
> return new EOKeyValueQualifier(Category.RUN_ID_KEY,
EOQualifier.QualifierOperatorEqual, runId());
> }
> ...
> public WOActionResults indexAction() {
> NSLog.debug.appendln("indexAction reached " + baseQualifier());
>
> ERXRestFetchSpecification<Category> fetchSpec = new
ERXRestFetchSpecification<Category>(Category.ENTITY_NAME, null,
baseQualifier(), queryFilter(), null, 25);
> return response(fetchSpec, showFilter());
> }
>
> Query sent:
>
> /ra/category.json?qualifier=parent='1669'
>
> Output:
>
> 14004 [WorkerThread15] DEBUG NSLog - indexAction reached (runId =
'20110723:11:50')
>
>
> queryFilter() has the line:
>
> filter.exclude(new ERXKey<String>("runId"));
>
> but removing that line has no effect.
>
>
> The values returned include all Category objects; however, I expected to
see only those matching the baseQualifier AND the URL specified qualifier;
is this correct? How do I achieve this result?
>
> Liz
>
> _______________________________________________
> 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/martin.samm%40aetopia.com
>
> This email sent to [email protected]
 _______________________________________________
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]

Reply via email to