-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Diffrent result using REST API 'api.parse.com' and 'Local parse server' #503
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
Can you put the actual output in a gist or a text file and attach it here, since we can't quite see the difference based on URLs, since the api keys/app ids are not specified. |
It doesn't look like the URLs are different, so lets not focus there... If you're still having an issue with the latest version, please open a new issue and describe the differences in the results. Thanks. |
@shebinceino Hi, I have a solution for this problem. |
Thanks. Its working |
I try to migrate my local server.
Migration was success.
But I have a problem while use REST API and same parameter.
These are parameters.
include:companyId.logo
limit:100
order:-createdAt
where:{"createdAt":{"$gte":"2016-02-17T15:00:00.000Z"},"visible":{"$ne":false}}
This is url for api.parse.com.
https://api.parse.com/1/classes/Job?include=companyId.logo&limit=100&order=-createdAt&where=%7B%22createdAt%22%3A%7B%22%24gte%22%3A%222016-02-17T15%3A00%3A00.000Z%22%7D%2C%22visible%22%3A%7B%22%24ne%22%3Afalse%7D%7D
This is url for local server.
http://www.easyk.co.kr/parse/classes/Job?include=companyId.logo&limit=100&order=-createdAt&where=%7B%22createdAt%22%3A%7B%22%24gte%22%3A%222016-02-17T15%3A00%3A00.000Z%22%7D%2C%22visible%22%3A%7B%22%24ne%22%3Afalse%7D%7D
Response is OK.
But results are not same.
Another case, results are same.
These are parameters.
include:companyId.logo
limit:200
order:-createdAt
where:{"expired_at":{"$gte":{"__type":"Date","iso":"2016-02-17T15:00:00.000Z"}},"visible":{"$ne":false}}
This is url for api.parse.com.
https://api.parse.com/1/classes/Job?include=companyId.logo&limit=200&order=-createdAt&where=%7B%22expired_at%22%3A%7B%22%24gte%22%3A%7B%22__type%22%3A%22Date%22%2C%22iso%22%3A%222016-02-17T15%3A00%3A00.000Z%22%7D%7D%2C%22visible%22%3A%7B%22%24ne%22%3Afalse%7D%7D
This is url for local server.
http://www.easyk.co.kr/parse/classes/Job?include=companyId.logo&limit=200&order=-createdAt&where=%7B%22expired_at%22%3A%7B%22%24gte%22%3A%7B%22__type%22%3A%22Date%22%2C%22iso%22%3A%222016-02-17T15%3A00%3A00.000Z%22%7D%7D%2C%22visible%22%3A%7B%22%24ne%22%3Afalse%7D%7D
These results are same.
Why not same upper case?
I don't know..
Parse server not fully support REST API?
Thanks,
p.s
I try change to Parse Javascript SDK. This way is OK. I think that 'createdAt' has problem using REST API.
The text was updated successfully, but these errors were encountered: