Skip to content

Finish moving query logic #1888

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

Merged

Conversation

drew-gross
Copy link
Contributor

DatabaseController.prototype.find no longer depends on the mongo format, I think. Except maybe in count results.

// Parse.com treats queries on _created_at and _updated_at as if they were queries on createdAt and updatedAt,
// so duplicate that behaviour here. If both are specified, the corrent behaviour to match Parse.com is to
// use the one that appears first in the sort list.
if (sort && sort._created_at) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need the undefined check for sort since you've specified the default value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably not. Will change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep it was unnecessary, tests passed without.

@ghost
Copy link

ghost commented May 24, 2016

@drew-gross updated the pull request.

@peterdotjs peterdotjs merged commit c4499d2 into parse-community:master May 24, 2016
@drew-gross drew-gross deleted the finish-moving-query-logic branch May 24, 2016 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants