-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Queries on relation fields with multiple ins do not work correctly. #1271
Comments
I've managed to reproduce this and am working on a fix. |
PS: thanks a lot for the extremely detailed bug report. I'm going to start pointing to this as a "perfect" bug report. |
drew-gross
added a commit
that referenced
this issue
Mar 31, 2016
flovilmart
added a commit
that referenced
this issue
Mar 31, 2016
Point to #1271 as how to write a good issue report
flovilmart
added a commit
that referenced
this issue
Mar 31, 2016
3 tasks
3 tasks
3 tasks
3 tasks
3 tasks
This was referenced Apr 1, 2016
3 tasks
This was referenced Apr 2, 2016
getting Error parse-server-push-adapter GCM send errored: 401 while sending push notifications
#1352
Closed
3 tasks
3 tasks
ghost
mentioned this issue
Apr 6, 2016
3 tasks
3 tasks
3 tasks
This was referenced Sep 13, 2016
4 tasks
4 tasks
ghost
mentioned this issue
Oct 13, 2016
4 tasks
4 tasks
4 tasks
4 tasks
4 tasks
4 tasks
4 tasks
4 tasks
This was referenced Jan 6, 2017
Closed
This was referenced Jan 16, 2017
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Steps to reproduce
See "queries on relation fields with multiple ins" case in ParseRelation.spec.js
Logs/Trace
The actual REST request generated by the case
Causes
multiple
$in
s on different relation fields end up having a merged$in
onobjectId
becomes
It is supposed to be like
The text was updated successfully, but these errors were encountered: