-
Notifications
You must be signed in to change notification settings - Fork 31
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
Criteria/properties order of MongoStore.query #37
Comments
Yes, this is on the list of todos, see #31. I think generally these were designed to reflect QueryEngine syntax. I'd prefer to keep query because it's similar to the rest interface and it's a bit distinct from find in that one can specify a list of properties as opposed to a dictionary for projection. |
Ah, my apologies for creating the duplicate!
…On Thu, Aug 23, 2018 at 23:17, Joseph Montoya ***@***.***> wrote:
Yes, this is on the list of todos, see #31
<#31>. I think generally
these were designed to reflect QueryEngine syntax. I'd prefer to keep query
because it's similar to the rest interface and it's a bit distinct from
find in that one can specify a list of properties as opposed to a
dictionary for projection.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC1rRD8F2cKhsJgexLJae8TNExut28YQks5uT5plgaJpZM4WKuHq>
.
|
@montoyjh FYI one can specify a list of properties to a pymongo collection’s |
I appreciate they're kwargs anyway, but is there a reason their order is reversed compared to pymongo? Think this might easily confuse people. (Also why
query
overfind
? for same reason)The text was updated successfully, but these errors were encountered: