-
Notifications
You must be signed in to change notification settings - Fork 284
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
add MongoCollection.aggregate helper method #348
Conversation
Can you please squash the commits into one? (http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) |
Bad idea, because GiHub says: "Warning: It is considered bad practice to rebase commits which you have already pushed to a remote repository. Doing so may invoke the wrath of the git gods" |
It's kind of acceptable if done on a branch that is only meant as the source for a pull request, though (or even necessary when the pull request gets out of date). But staying on topic, otherwise everything looks good to merge..... now you closed it! ;) |
@japplegame |
@japplegame Thanks a lot, looks good now. Mind if I reopen and pull in this state? |
Whoaaa. I'm really confised with GitHub. Shame! |
Hm... right there are actually four commits now ;) |
Now it looks OK again. Kind of weird to observe real-time updates on github. |
One commit again :D |
Ok. :) |
Yes (though @s-ludwig can do it on his own) |
Add MongoCollection.aggregate helper method
Success! :) |
Description: http://docs.mongodb.org/manual/reference/method/db.collection.aggregate
According to description, aggregate should return object with array of documents and status code. But this implementation returns just array of documents, because status code is always equal 1 and completely useless.