Node MongoDB execution order

Question

I'm using collection.insert then in the callback collection.findAndModify

About 10% of the time collection.findAndModify fails to find the document I just inserted, even though it's being executed after the insert callback. Why is this possible? How do I deal with that?

enter image description here

I insert it, then try to modify it, but it's not there, then try to modify it again and it's there.

ma08 · Accepted Answer · 2014-08-07 06:46:04Z

1

You should give the second command in the callback as the insert is asynchronous. If you are using the mongodb native driver for node,

collection.insert(document, function(err, records){
     //call collection.findAndModify here

});

Check the docs

answered Aug 7, 2014 at 6:46

ma08

3,7644 gold badges26 silver badges36 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Farzher Over a year ago

Yes, I am using npm mongodb, and this is exactly what I'm doing, I'm using collection.insert then in the callback collection.findAndModify I guess I'll need to create a simple way to replicate the issue

ma08 Over a year ago

@StephenSarcsamKamenar Sorry I overlooked that part in your question. All hell will break loose if this is true, something must be wrong.

wdberkeley Over a year ago

Yes, please add as simple a code snippet as you can find to recreate the issue.

Collectives™ on Stack Overflow

Node MongoDB execution order

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related