I’m using Mongoose. This works for me, I’m simply using this as a reference to the model. I have a Comment model. Comments can have a reply that is also Comment. var Comment = new mongoose.Schema({ id: { type: ObjectId, required: true }, comment: { type: String }, replies: [ this ], });
You can check the object’s prototype via the instanceof operator to confirm it’s an instance of your mongoose model. Using the example schema from mongoosejs.com: if (obj instanceof Cat) { // yes, it’s a mongoose Cat model object … }
@aheckmann reply at github schema.pre(‘save’, function (next) { this.wasNew = this.isNew; next(); }); schema.post(‘save’, function () { if (this.wasNew) { // … } }); isNew is an key used by mongoose internally. Saving that value to the document’s wasNew in the pre save hook allows the post save hook to know whether this was an … Read more
You can also explicitly specify only required parameters of populate: Group .find({}) .populate({path: ‘Members’, options: { sort: { ‘created_at’: -1 } } }) Have a look at http://mongoosejs.com/docs/api.html#document_Document-populate
Populate will automatically replace the specified path in the document, with document(s) from other collection(s). Your example Story.findOne({ title: Nintendo }) will return a Story of this kind: { _creator : A0jfdSMmEJj9, // example value title : Nintendo, fans : [r432i900fds09809n, fdsjifdsjfueu88] // example values } } That kind of request would be enough when … Read more
My understanding on the official documentation is that generally when there is only one connection mongoose.connect() is use, whereas if there is multiple instance of connection mongoose.createConnection() is used. Yes. To be exact, .connect() creates actually a pool of sockets/connections (defined in poolSize in the connection settings, the default is 5) it keeps open, so … Read more
By default (in an effort to minimize data stored in MongoDB), Mongoose will not save empty objects to your database. You can override this behavior by setting the minimize flag to false when you create your schema. For example: const schema = new Schema({ star_info: { type: Schema.Types.Mixed, default: {} } }, { minimize: false … Read more
This function differs slightly from Model.findOneAndRemove() in that findOneAndRemove() becomes a MongoDB findAndModify() command, as opposed to a findOneAndDelete() command. For most mongoose use cases, this distinction is purely pedantic. You should use findOneAndDelete() unless you have a good reason not to. the offical site https://mongoosejs.com/docs/api.html#model_Model.findOneAndDelete
As of Mongoose 4.0 you can run validators on update() and findOneAndUpdate() using the new flag runValidators: true. Mongoose 4.0 introduces an option to run validators on update() and findOneAndUpdate() calls. Turning this option on will run validators for all fields that your update() call tries to $set or $unset. For example, given OP’s Schema: … Read more
You can do that with a single upsert: var obj = req.body; var id = obj._id; delete obj._id; if (id) { Model.update({_id: id}, obj, {upsert: true}, function (err) {…}); } The caveat is that your model’s defaults and middleware (if any) will not be applied. Mongoose 4.x Update You can now use the setDefaultOnInsert option … Read more