Skip to content
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

Merged
merged 1 commit into from
Oct 18, 2013
Merged

add MongoCollection.aggregate helper method #348

merged 1 commit into from
Oct 18, 2013

Conversation

japplegame
Copy link
Contributor

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.

@mihails-strasuns
Copy link
Contributor

Can you please squash the commits into one? (http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)

@japplegame
Copy link
Contributor Author

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"

@japplegame japplegame closed this Oct 18, 2013
@s-ludwig
Copy link
Member

"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 reopened this Oct 18, 2013
@japplegame japplegame closed this Oct 18, 2013
@mihails-strasuns
Copy link
Contributor

@japplegame
GitHub says a lot of wrong things about git :P
For pull request branches it is not only fine but almost necessary as their commits will go upstream as-is upon merging and having a clean history helps a lot in the long term.

@s-ludwig
Copy link
Member

@japplegame Thanks a lot, looks good now. Mind if I reopen and pull in this state?

@japplegame
Copy link
Contributor Author

Whoaaa. I'm really confised with GitHub. Shame!
I deleted branch and created a new. Now I can create new pull request :)

@s-ludwig
Copy link
Member

Hm... right there are actually four commits now ;)

@s-ludwig
Copy link
Member

Now it looks OK again. Kind of weird to observe real-time updates on github.

@mihails-strasuns
Copy link
Contributor

One commit again :D
@japplegame all you needed to do is git push -f origin mongo_aggregate after squashing :)

@japplegame
Copy link
Contributor Author

Ok. :)
What should I do now? Just reopen pull request?

@mihails-strasuns
Copy link
Contributor

Yes (though @s-ludwig can do it on his own)

@japplegame japplegame reopened this Oct 18, 2013
s-ludwig added a commit that referenced this pull request Oct 18, 2013
Add MongoCollection.aggregate helper method
@s-ludwig s-ludwig merged commit 42bc2de into vibe-d:master Oct 18, 2013
@s-ludwig
Copy link
Member

Success! :)

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.

3 participants