Invalid key name: $relatedTo with Parse.Query.and

[elios264]

Issue Description

Parse server is rejecting Parse.Query.and queries in conjution with relations, Parse.Query.or is working correctly.

my usecase is sending a push notification with complex query. therefore I need the Parse.Query.and

Steps to reproduce

Not working:

Working:

Expected Results

$relatedTo to be supported.

Actual Outcome

an exception.

Environment Setup

• Server

  • parse-server version (Be specific! Don't say 'latest'.) : 2.7.4
  • Operating System: windows
  • Hardware: my pc
  • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): local

• Database

  • MongoDB version: n/a
  • Storage engine: n/a
  • Hardware: n/a
  • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): mLab

[flovilmart]

Can you try with:

const installationsQuery = Parse.Query.or(....)
installationsQuery.equalTo('enabled', true);
installationsQuery.exists('user');

Also please provide the server logs when running with VERBOSE=1

[elios264]

Hey @flovilmart,

These are the verbose logs, before trying your approach:

Your workaround worked nice so far, I'll keep testing and if I encounter another case parse fails, I'll post it here.

I really appreciate your help, Thanks!

[flovilmart]

Actually the workaround is the original way of doing it. The and operator has been added lately and as you noticed, may be problematic. I’ll fix the issue in a shot future.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[LMBernardo]

Can we re-open this issue? It seems to still exist in the current version of parse-server. I'm not sure how to apply the workaround above to my situation - I definitely need AND, not OR.

EDIT: I figured out how to use the above workaround, thanks! I think this is still an issue and should be fixed within the SDK though.