Mongoose doesn’t remove existing indexes so you’ll need to explicitly drop the index to get rid of it. In the shell: > db.items.dropIndex(‘assets.serial_1’) This will happen if you initially define that field unique: true but then later remove that from the schema definition or change it to unique: false.
what corresponds to the “case” SQL statement in the aggregation framework, is the $cond operator (see manual). $cond statements can be nested to simulate “when-then” and “else”, but I have chosen another approach, because it is easier to read (and to generate, see below): I’ll use the $concat operator to write the range string, which … Read more
Perhaps you can use aggregation and an artificially high end date: c = db.foo.aggregate([ {$project: { next_time: 1, nlt: { $ifNull: [ “$next_time”, new ISODate(“9000-01-01”) ] } } } , {$sort: { “nlt”: 1}} ]); c.forEach(function(r) { printjson(r); }); Alternatively, if the majority of the material has nulls and you don’t want to deal with … Read more
The publish function determines which records should be synced to the mini-mongo database of any subscribing clients. So sorting the data in the publish function actually has no effect on the client, as the client-side database will likely store them in some other way. Of course you may want to use sort in a publisher’s … Read more
Use $in For the query in the question, it’s more appropriate to use $in db.Profiles.find ( { “name” : { $in: [“gary”, “rob”] } } ); Why doesn’t it work There’s a missing quote – the cli is waiting for you to finish the second part of your or: db.Profiles.find ( { $or : [ … Read more
There is some confusion between the Mongo extension and the MongoDB extension which are not the same. Because of your version number, I guess you are using the old Mongo extension that is deprecated. Make sure that you install the new MongoDB extension and you should be fine. Don’t forget to remove the old extension=mongo.so … Read more
Multiple updates may be performed on the same document, as long as those updates do not conflict (hence the “have conflicting mods in update” error). Because “$push” : {“bugs” : [{“name”:”bug1″, “count”:1}]} and “$inc” : {“bugs.0.count” : 1} are both attempting to modify the same portion of the document (namely the “bugs” array), they conflict. … Read more
So what this very much looks like is that you have already created collections in an existing database and now you are trying to access these with mongoose models. The problem is that mongoose uses some defaults which you may not be aware of, so the example you are showing from the shell is not … Read more
this is a case where you are adding the model to the global mongoose object but opening a separate connection mongo.createConnection() that the models are not part of. Since the model has no connection it cannot save to the db. this is solved either by connecting to mongo on the global mongoose connection: var connection … Read more