-
-
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
Support for nested .select()
calls
#2737
Conversation
Fixes #2653 Updated to use native field select in mongo and postgres |
@flovilmart updated the pull request - view changes |
Great job, I came up with the problem on Friday and this comes up on Monday, thanks for the work. |
@zenithanu glad to help! Once reviewed and merged, this will be available by pointing your parse-server to |
is there any way to stop nested select future after update server . because all my queries will fail and I will use this in future after update my apps thanks |
@oazya500 what would fail in your app? |
ParseQuery quere = ParseQuery.getQuery("MSGES");
my old apps like above . so if I update server all my old apps will not git name for user or CATOGREY and I should do like this in new app and I want to updat server becuse I have this error in my server ParseError { code: 101, message: 'Object not found.' } and server restart after this error app restart every 10 minute at most │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │ |
The previous behavior is still valid with that PR. Because you call include(). The update you suggest would just return the name key of that object, and not the whole object. |
it Supposed to be valid but Unfortunately not valid . give it try and you see it not valid even with include() |
did you mean for update I should do like this quere.selectKeys(["user", "CATOGREY", "user.name", "CATOGREY.name"]); |
quere.selectKeys(["user", "CATOGREY", "user.name", "CATOGREY.name"]); |
even with beforeFind not valid Parse.Cloud.beforeFind('MSGES', (req) => { |
quere.selectKeys(["user", "CATOGREY", "user.name", "CATOGREY.name"]); that for future I was do that but parse-server not support it before 2.2.22 |
any update how to stop nested select in new update |
You can't disable that feature and it's unlikely to be removed as It was a bug compared to parse.com |
for other problem what I can do the problem is ParseError { code: 101, message: 'Object not found.' } and server restart after this error app restart every 10 minute at most |
@oazya500 your server should not restart when logging an error. Are you using pm2 and monitoring the logs? |
@flovilmart all off this app using parse server and one off them restart 260 times in tow day |
|
keys
property in RestQuery when it contains nesting.Fixes #1567