-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Using includeKey: on array of pointers results in error #1293
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
What do you expect to happen? Have the pointers loaded from the array? Or just not having an error? |
I expect it to load the pointers from the array. This is how it works on the Parse hosted app and what the documentation says to do. |
Alrighty! |
I just tried to reproduce the error and I can't reproduce it. |
Ok, here's a sample array
Where |
Can you check the commit that is referenced here and tell me if that embodies your issue? |
Any news on that? |
It looks like it may fix my issue but I have only been able to successfully set up parse-server using the 2.2.4 release on Note: I tried setting up my |
Yeah, you can't set it up like that as the git repository don't hold the lib. |
I meant that 2.2.4 is the latest version that I was able to install successfully and it doesn't contain the commit you referenced so I haven't been able to test the fix. The issue still exists in 2.2.4. |
Oh right. I'll reopen then and we'll see when 2.2.5 is out |
Ok. Thanks @flovilmart, I appreciate your help. |
2.2.5 is out! have it a go and let us know! |
No luck. I installed 2.2.5 but I'm still getting the same error. I'm trying to think of things that might help with troubleshooting. I'll comment here if I come up with anything. |
If you look at the test case here, that seem exactly what you're describing |
Yeah, it seems like it should work but I keep getting the error. I decided to run parse-server from master locally using the instructions here and this is the log output when I run the query in question:
|
Check the _SCHEMA class and find the _User row... Is the column you're including definitely an array column? |
Just checked and it's definitely an array. This is what it looks like:
|
Can you check where the |
Looks like the error occurs in the second case:
More specifically, |
try console.log the object? |
Here's the log of the object: |
Maybe because they have been improperly stored... Are all your objects like that? What's your client code that creates those objects? try removing the throwing, and ignore the unproperly configured objects by returning an empty array, see if many/most of those are improperly stored. |
Yeah, that was the problem. I remember we had some issues with this array when adding a web client. Anyway, I found two users that had bad arrays. After I removed the bad arrays the query worked perfectly. I guess on the Parse hosted apps the bad arrays are ignored. Thanks again for all your help, it is truly appreciated. |
May be, let's close that for now. |
I have the same problem with arrays of PFUsers and PFFIles. |
I am also getting arrays of pointers like this in my database sometimes: Instead of |
In a query when I do this
Funny how if I remove that |
Hello, same error we see here. An array of PFObjects are only returning partial data instead of full, even with includeKey. It works fine with just a single pointer however. |
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!
Environment Setup
Local
Xcode 7.3
iPhone 6s simulator with iOS 9.3
Parse-iOS-SDK 1.13
Remote
heroku/nodejs
parse-server 2.2.4
parse 1.8.1
Steps to reproduce
Precondition: There exists an object on the database that has an array of pointers as one of its fields.
PFQuery
on the object's type.includeKey:
Note: This works correctly my Parse hosted app. It only becomes an issue when I try to use my parse-server hosted on heroku.
Logs/Trace
[Error]: can only include pointer fields (Code: 102, Version: 1.13.0)
The text was updated successfully, but these errors were encountered: