node-mongodb-native

问题 The documentation for the node-mongo-native collection.find() function says that it creates a cursor object which lazily returns the matching documents. Furthermore: The basic operation on a cursor is the nextObject method that fetches the next matching document from the database. The convenience methods each and toArray call nextObject until the cursor is exhausted. Unfortunately, the documentation provides no indication of how to tell when the cursor is actually exhausted. You could use the

问题 I'm using native mongo driver in Joyent cloud, the node.js application runs fine locally but in Joyent when i run with usrname/pswd that they provided it fails to connect. following is the code used to connect: var db = new MongoDB(dbName, new Server('localhost', 27017 , {auto_reconnect: true}), {w: 1}); db.open(function(e, db){ if (e) { console.log(e); } else{ console.log('connected to database :: ' + dbName); //db.admin().authenticate('admin', '+(uihghjk', function(de , db){ // if(e){ //

问题 I'm wondering what the most efficient way to manually abort a running query with the official node client is. In my current code I am creating a new DB connection for each remote client and then simply closing those connections if the client disconnects early, which works well but seems like it might be a wasteful way of doing things (edit: indeed it is; detailed here) . I imagine if it's possible to directly access the mongodb client connection pool and close specific connections rather than

问题 My database object has an optional property named tags which is a string array. I want to write a query that returns objects if they match one of these conditions: They don't have a tags property. They have a tags property that has at least one item included in another array called queryTags From reading the documentation I came up with the following but it doesn't work: let query = { tags: { '$or': [{'$exists': false}, {'$in': queryTags}]} } 回答1: $or is a top-level operator, so your query

问题 Is there any way of implementing a counters collection as described in the docs with node-mongodb-native? I'm trying to avoid doing this by nesting over 9000 callbacks (which IMHO sounds untidy and not-elegant) but the good people who wrote this native driver refused to implement synchronous/blocking calls. Does the native driver provide a someway to call user defined functions and use their return values during queries? Or could there be an alternate way of extracting a sequential count...

问题 I'm using Node.js and Angular.js for a web project. I understand that date is saved as date if it's created on server using new Date() (e.g. 2015-04-08 04:15:18.712Z shown in Robomongo as Date type). However, if the date is created on client using new Date(), it is then saved as a string (e.g. 2015-04-07T04:58:12.771Z shown in Robomongo as String type), because it becomes a string through node API. How to make it save as a Date instead of String? UPDATE: This is what I got based on Jason Cust

问题 I am using official node-mongodb-native driver in my project. Which was installed by doing npm install mongodb. However I want to check its version but not sure how to do so. There is nothing in the READ.ME file of that npm repo. Please help. Thanks. 回答1: According to the npm documentation you can get a list of npm packages and their corresponding versions using npm ls or npm ls -g (for global) 回答2: The version is exported in index.js: exports.version = require('../../package').version; So

问题 I want to enable profiling on one of my MongoDB databases, via the node-mongodb-native driver. However there doesn't seem to be a Db.setProfilingLevel() method (apart from on the Admin DB). I've tried using db.command({setProfilingLevel: 2}) but get no such cmd: setProfilingLevel . Works fine through the mongo shell with db.setProfilingLevel(2) 回答1: I see what you mean about the methods, but I think the issue with the db.command attempt is that you are trying to run a shell helper as a

问题 I am using node + express to create a simple REST API, and am trying to separate out routing logic from db logic. I am having a problem getting access to the DB from the routes. Here is my server.js code: var express = require('express') , path = require('path') , http = require('http') , mongo = require('mongodb'); // Configure Express app var app = express(); app.configure(function () { app.set('port', process.env.PORT || 3000); app.use(express.logger('dev')); /* 'default', 'short', 'tiny',

问题 Using the native 'mongodb' npm package, I'm receiving Error: connection closed due to parseError When making a very basic query: collections.myCollection.findOne({id: someID}, function (err, repo) { ... }) The weird thing is, the exact same query has run before. Types are identical for each query, etc. 回答1: Answering my own question to hopefully stop the next person from tearing their hair out: As noted here, this error message is useless and doesn't relate to the actual problem. The