-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
select constraint only works on top level object #3381
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
This feature is heavily tested here: https://github.com/ParsePlatform/parse-server/blob/master/spec/ParseQuery.spec.js#L2617 Can you please check what's different, From the request, I can see in the |
thanks @flovilmart Good catch on the request. I tested a few variations, with and without "client" in the select array, same result for both. After looking over the spec (thanks for the link), the issue looks to be related to datatypes. I have the Class Item, which has a object column client, not a pointer to a related class. |
Uhm... not sure we support that case then. Do you wanna try implement it? |
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. |
@adammaddox did you manage to solve this? |
Steps to reproduce
Expected Results
Actual Outcome
Environment Setup
Server
Database
Logs/Trace
You can turn on additional logging by configuring VERBOSE=1 in your environment.
The text was updated successfully, but these errors were encountered: