Assuming, var friend = { firstName: ‘Harry’, lastName: ‘Potter’ }; There are two options you have: Update the model in-memory, and save (plain javascript array.push): person.friends.push(friend); person.save(done); or PersonModel.update( { _id: person._id }, { $push: { friends: friend } }, done ); I always try and go for the first option when possible, because it’ll … Read more
As noted, the order of the arguments in the array of an $in clause does not reflect the order of how the documents are retrieved. That of course will be the natural order or by the selected index order as shown. If you need to preserve this order, then you basically have two options. So … Read more
With a modern MongoDB greater than 3.2 you can use $lookup as an alternate to .populate() in most cases. This also has the advantage of actually doing the join “on the server” as opposed to what .populate() does which is actually “multiple queries” to “emulate” a join. So .populate() is not really a “join” in … Read more
General Scope and Explanation There are a few things wrong with what you are doing here. Firstly your query conditions. You are referring to several _id values where you should not need to, and at least one of which is not on the top level. In order to get into a “nested” value and also … Read more
The second option is a real lack of security. It means that you will send to your users your mongodb login/password or even worse give them a non secured mongodb url. To you really want that your user can see other users data ? You should definitely use the first solution with a middleware. Further … Read more