select() constraint is not applied to included objects

I am running this same query from parse.com and on my local parse server .

var messageQuery = new Parse.Query("Message");
    messageQuery.descending("updatedAt");
    messageQuery.include("channelId");
    messageQuery.select("channelId");
    messageQuery.select("channelId.exchange");

Channeld is pointer field to my other document.
On parse.com server this query works and return result with only exchange field and on parse-server it selects complete channelId document and prints everything.

Also select works when i am not expanding any pointer fields.

Can you include more information, such as example responses that clearly show the difference?

Please refer to this issue for an example of a great bug report.

I got same issue with Parse Server, when migrating from Parse.com.

This works fine for getting whole sender fields of a message, where sender is Parse.User object.

var messageQuery = new Parse.Query(Message);
messageQuery.descending('createdAt');
messageQuery.limit(1);
messageQuery.include(['sender']);
messageQuery.select(['type', 'body', 'isRead', 'sender']);
return messageQuery.first({useMasterKey: true});

But if I restrict select parameter to 'sender.phone' from 'sender' like this,

var messageQuery = new Parse.Query(Message);
messageQuery.descending('createdAt');
messageQuery.limit(1);
messageQuery.include(['sender']);
messageQuery.select(['type', 'body', 'isRead', 'sender.phone']);
return messageQuery.first({useMasterKey: true});

no sender information is acquired.

parse-server@2.2.13

really a big issue, can only work around on cloud side now.

I have the same problem. It worked great on parse.com, but not on the parse server.

It seems like the issue is clear at this point: the select() constraint on Parse Server only works for fields on the top level object. It seems like there's interest in replicating parse.com's select() behavior on Parse Server. If someone wants to send a PR to add this enhancement to Parse Server we can take a look.

+1

Reproduction for #1567

Support for nested `.select()` calls (#2737)

I'm still having trouble with this same issue. Was this ever addressed?

@dbloembe

@dbloembe please open a new issue with all relevant informations

Navigation Menu

Repository navigation

select() constraint is not applied to included objects #1567

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

select() constraint is not applied to included objects #1567

Description

Activity

devshop9 commented on Apr 20, 2016

hramos commented on Apr 20, 2016

MasaGon commented on Jun 17, 2016

Poordeveloper commented on Jul 9, 2016

Ishimilated commented on Jul 24, 2016

hramos commented on Jul 25, 2016

ossamaweb commented on Aug 11, 2016

dbloembe commented on Aug 8, 2018

flovilmart commented on Aug 8, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions