Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

Node.JS MongoDB Order of Operations Use Case

Node.JS MongoDB Order of Operations Use Case


What is the order of operations for the mongodb-native driver?

Let's say you have a class that's purpose is to save a document of some sort and let's say it has a long life. How many times should open be called? Once per db write? When is close supposed to be called? Essentially I want a class method that looks like this:

  var myMongoClass = new MongoDB(server,port)

I posted this a while ago and got it working: Problem with MongoDB GridFS Saving Files with Node.JS

It's now not working at all and failing with TypeError: Cannot read property 'md5' of null

Every time I work with this library I want to bang my head through a wall.

Problem courtesy of: Justin Thomas


It seems like the correct answer is create a client and keep that client open for the duration of the application (never explicitly calling close). I have a wrapper that keeps a reference to the connected client and my app only boots up if the connection is received.

Solution courtesy of: Justin Thomas


View additional discussion.

This post first appeared on Node.js Recipes, please read the originial post: here

Share the post

Node.JS MongoDB Order of Operations Use Case


Subscribe to Node.js Recipes

Get updates delivered right to your inbox!

Thank you for your subscription