-
-
Notifications
You must be signed in to change notification settings - Fork 599
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
query.include is not including what it should #32
Comments
just tried changing Parse version to latest instead of 1.6.4 and query.include is working. I wonder what is the problem with setting the Parse version to 1.6.4 through parse jssdk 1.6.4? |
Thank you for your feedback. We prioritize issues that have clear and concise repro steps. Please see our Bug Reporting Guidelines about what information should be added to this issue.
|
Here is the code:
Here is what I get for the field pdName for version 1.6.4:
Here is what I get for the field pdName with either version: latest or 1.6.2
It seems that latest is not pointing to 1.6.4 because I still have the same parent not defined error when using it, but when I change to 1.6.4 the relation error is not happening, but the query.include one yes. I hope I made myself clear. |
This might be an issue with caching on our cloud code servers. I'll kick off a cache flush and see if latest then points to 1.6.4 as it should. |
"latest" now appears as 1.6.4 for me. Check if you're still having issues, @marlonguerios |
I can confirm that 1.6.2 works and 1.6.4 does not. |
Same here. Now latest is pointing to 1.6.4, but I still have the problem with query.include not returning the included object. |
Same issue here, my cloud code just stopped working, not included objects anymore :( |
From my investigation, it seem that this only affects the results of queries made in cloud code (the query fetches the nested objects, they are available in cloud code, but when they return to the client they are pointers). Is that in line with what everyone here is experiencing? |
@andrewimm same behavior here. |
Sorry all, I believe this was an oversight introduced in f2d35f2. We didn't realize this would affect nested queries coming back from cloud code, but we should have a fix in later today. In the meantime, we've added tests for returning nested query results to our Cloud Code suite, so that we'll notice beforehand if something here breaks again. |
1.6.6 fixes this. It's out on npm now, and is currently being deployed to cloud code. I'll follow up when that process has completed. |
This happened last night. 1.6.6 is available everywhere, and should fix this issue. "latest" on cloud code should also point to 1.6.6 |
can you check this works with dotted dotted includes? e.g. x.y , myObject.createdUserRef I am trying to get this to work and it works at the first level now, but doesn't seem to traverse |
is 'seen' in toJSON too simple? what about scenario where there are 2 pointers to the same object, but for different reasons and you want to expand 1. e,g, "createdUserRef": { here the createdBy user and the user are different things that happen to point to the same _User |
@swilli40, we tried passing |
@swilli40 actually, I take that back. It looks like the original attempts were complicated by the same issue I hit with the eventually-merged solution: the exported version of |
It might need a leaf first crawler as converting a parse object to object means lower objects with attributes won't be expanded. Bottom up would prevent this issue. |
any news on this one? |
This should have been fixed in 1.6.8, which is currently on npm and will go out to cloud code later today |
great. thanks |
Andrew, not fixed, built the 1.6.8 and debugged locally. Same issue with dotted includes. x.y |
Hey, I'm experiencing the same issue in 1.9. var query = new Parse.Query('TimeEntry');
var date = request.param.date;
date.setHours(0, 0, 0, 0);
query.greaterThanOrEqualTo('endDate', date);
date.setHours(23, 59, 59, 999);
query.lessThanOrEqualTo('startDate', date);
query.ascending('startDate');
query.include('project'); However the result does not include e.g. the project title or the color (both String).
I even tried to extend the Parse.Object like this and call the query correspondingly but with no result, except that the 'project' becomes a ParseSubclassObject. var TimeEntry = Parse.Object.extend('TimeEntry');
var Project = Parse.Object.extend('Project');
var query = Parse.Query(TimeEntry); What else can I do? |
@mbruschi the The fact that |
But m having the same issue with 1.9.2 included key shows fully in network response but |
the same issue in 2.4.0
billboard is a column name (pointer) |
After I changed the Parse version to 1.6.4, query.include stopped working and it is not including the data from the pointer. There was no changes to my code, only the Parse version. When I revert Parse version back to 1.6.2 query.include is works fine again, but I can't use 1.6.2 because of the Relations bug that was fixed on 1.6.4.
The text was updated successfully, but these errors were encountered: