TypeError: db.collection is not a function

by

So I voted for the answer which said to just go down to mongodb 2.2.33 because I tried it and it worked, but then I felt weird about just downgrading to fix a problem so I found the solution which allows you to keep version >= 3.0. If anyone finds this issue and their problem wasn’t passing in a blank reference like the accepted answer, try this solution out.

When you run..

MongoClient.connect(db.url,(err,database) =>{ }

In mongodb version >= 3.0, That database variable is actually the parent object of the object you are trying to access with database.collection('whatever'). To access the correct object, you need to reference your database name, for me that was by doing

MongoClient.connect(db.url,(err,database) =>{ 
  const myAwesomeDB = database.db('myDatabaseNameAsAString')
  myAwesomeDB.collection('theCollectionIwantToAccess')
}

This fixed my errors when running my node.js server, hopefully this helps somebody who doesn’t just want to downgrade their version.

(also, if you don’t know your db name for some reason, just do a console.log(database) and you’ll see it as an object attribute)

EDIT (June 2018):

According to this, the callback actually returns the connected client of the database, instead of the database itself.

Therefore, to get the database instance, we need to use this method, which takes in a dbName. In the documentation it said If not provided, use database name from connection string., as mentioned by @divillysausages in the comments below.

In short, we should call database.db().collection('theCollectionIwantToAccess'); if the dbName is provided by url, where the database is actually client for better understanding

More Related Contents:

  1. Unable to delete data from mongoDB
  2. collection is not defined in mongodb
  3. No ‘Access-Control-Allow-Origin’ – Node / Apache Port Issue
  4. Push items into mongo array via mongoose
  5. Avoid “current URL string parser is deprecated” warning by setting useNewUrlParser to true
  6. Cannot overwrite model once compiled Mongoose
  7. MongoDB/Mongoose querying at a specific date?
  8. Allow CORS REST request to a Express/Node.js application on Heroku
  9. How to use a variable as a field name in mongodb-native findOne()?
  10. How to implement a secure REST API with node.js
  11. add created_at and updated_at fields to mongoose schemas
  12. How to populate a sub-document in mongoose after creating it?
  13. mongoose custom validation using 2 fields
  14. Stream from a mongodb cursor to Express response in node.js
  15. How to protect the password field in Mongoose/MongoDB so it won’t return in a query when I populate collections?
  16. How to get a callback on MongoDB collection.find()
  17. Error: getaddrinfo ENOTFOUND in nodejs for get call
  18. MongoNetworkError: failed to connect to server [localhost:27017] on first connect [MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017]
  19. Mongoose update without callback
  20. How to fix ‘Error: querySrv EREFUSED’ when connecting to MongoDB Atlas?
  21. What is best way to handle global connection of Mongodb in NodeJs
  22. Model.find() returns empty in mongoose [duplicate]
  23. Mongoose – caused by :: 11000 E11000 duplicate key error index?
  24. How can I use a cursor.forEach() in MongoDB using Node.js?
  25. ExpressJS : How to redirect a POST request with parameters
  26. Node.js (with express & bodyParser): unable to obtain form-data from post request
  27. Why can I execute code after “res.send”?
  28. How to send an html page as email in nodejs
  29. Model.find().toArray() claiming to not have .toArray() method
  30. MongoError: connect ECONNREFUSED 127.0.0.1:27017

Leave a Comment