-
-
Notifications
You must be signed in to change notification settings - Fork 597
doesNotMatchKeyInQuery doesn't work when using same query and key with different query key #621
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for your question! We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Parse Server. Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #parse.com? We'll be happy to answer there. Post a link to your Stack Overflow question here, so that we don't lose track of it. You may also use Server Fault for questions about managing your own servers. |
@tgreco I don’t think you can use it twice in the same query. One will override the other because it’s key value and you can have one key in this case owner. Try using an |
@dplewis my issue with a compound query is that this query is much more complex and uses GeoPoints and near in a subquery so I cannot include that in my compound query as the documentation says:
How could I include compoundPhotoQuery into the main PhotoQuery now? |
Uh oh!
There was an error while loading. Please reload this page.
My schema:
I want to find photos for users that do not have any matches.
What I tried:
This only works for the scheduledBy column.
Seems like you can't do doesNotMatchKeyInQuery with the same key and query but different query keys for some odd reason.
Can anyone confirm this? If so what would be the best alternative?
I removed scheduledBy and used scheduledWith only and that worked as well. So it's not something wrong with the data it's a bug with Parse I believe.
The text was updated successfully, but these errors were encountered: