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

Copy Collections using forEach #1279

Closed
manestream opened this Issue Jan 28, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@manestream

manestream commented Jan 28, 2017

RoboMongo 0.9.0 does not execute the following statement properly:

db.getCollection('origin').find({context:'0'}).forEach(function(e){db.getCollection('target').insert(e)});

Sometimes the exeuction copied some 1000s documents. Sometimes it just ended up copying nothing.

I am using MongoDB 3.4.1 and used the above statement as is. The collections are in the same database. The statement executes properly in the mongo shell.

Thanks a lot !

Cheers
Kai²

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jan 30, 2017

Collaborator

Hi @manestream, thank you for reporting!
Could you please try this solution, it solved a lot of problems in the past: #1106 (comment)

Please let us know how it went.

Collaborator

juliashibalko commented Jan 30, 2017

Hi @manestream, thank you for reporting!
Could you please try this solution, it solved a lot of problems in the past: #1106 (comment)

Please let us know how it went.

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jun 29, 2017

Collaborator

Checked in Robo3T 1.1. Can't reproduce the issue. Closing as can't reproduce.
Please check the latest version as we implemented MongoDB 3.4 support and changing shell Timeout from UI (see here http://blog.robomongo.org/robomongo-is-robo-3t/#4a).
Feel free to re-open in any case.

Collaborator

juliashibalko commented Jun 29, 2017

Checked in Robo3T 1.1. Can't reproduce the issue. Closing as can't reproduce.
Please check the latest version as we implemented MongoDB 3.4 support and changing shell Timeout from UI (see here http://blog.robomongo.org/robomongo-is-robo-3t/#4a).
Feel free to re-open in any case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment