mongoose-schema

I'm trying to validate some data that will be inserted into a new document, but not before a lot of other things need to happen. So I was going to add a function to the static methods that would hopefully validate objects in an array against he model schema. Heres the code thus far: module.exports = Mongoose => { const Schema = Mongoose.Schema const peopleSchema = new Schema({ name: { type: Schema.Types.String, required: true, minlength: 3, maxlength: 25 }, age: Schema.Types.Number }) /** * Validate the settings of an array of people * * @param {array} people Array of people (objects) *

I have a model that keeps erroring out after the first POST. I'm creating a scheduling application, which is X number of days, with rooms, and time slots for the rooms. The issue I'm having is creating Day Objects in the database. For sake of easy reading I'm just going to have a single key value pair day.model.js var mongoose = require('mongoose'); // Day Schema var daySchema = mongoose.Schema({ name:{ type: String, required: true, }, createdAt:{ type: Date, default: Date.now } }); var Day = module.exports = mongoose.model('Day', daySchema); // Get all Days module.exports.getDays = function

I want to start taking advantage of Mongooses document versioning (__v key). I was having an issue actually incrementing the version value, then I found that you have to add this.increment() when executing a query. Is there a way to have automatically incremented? For now, I just added it to the pre middleware for a update-type queries: module.exports = Mongoose => { const Schema = Mongoose.Schema const modelSchema = new Schema( { name: Schema.Types.String, description: Schema.Types.String } ) // Any middleware that needs to be fired off for any/all update-type queries _.forEach( [ 'save',

I've encountered a strange thing. I have several mongoose models - and in one of them (only in one!) I get this error: TypeError: Schema is not a constructor I find it very strange as I have several working schemas. I tried logging mongoose.Schema in the non-working schema and it is indeed different from the mongoose.Schema in my working schemas - how is that possible? The code is almost identical. Here's the code for the non-working schema: var mongoose = require('mongoose'); var Schema = mongoose.Schema; var errSchema = new Schema({ name: String, images:[{ type:String }], sizes:[{ type:

I have a use case where the database is modelled like this: name: XYZ gradeCards: [{ id: 1234, // id of the report card comments: ['GOOD','NICE','WOW'] }, { id: 2345, comments: ['GOOD','NICE TRY'] }] Now, I have a query that I would like to query the schema as follows: I would be given a list of ids and values. For example: the given list is as follows: [{ id: 1234, comments: ['GOOD','NICE'] },{ id: 2345, comments: ['GOOD'] }] In short the ID should be matching and the comments should be a sub-array of the comments array for that id and also, all the conditions specified in the array should be

The structure of the project is structure The main file is index.js that is located in the main directory. This one has 'use strict' var mongoose = require('mongoose'); var app = require('./app'); var port = process.env.port || 3000; mongoose.connect('mongodb://localhost:27017/changeProducts',(err,res) =>{ if(err){ throw err; }else{ console.log("Base de datos funcionando correctamente.."); app.listen(port, function(){ console.log('Servidor nodejs corriendo(app.listen)... '); }); } }); The version of mongoose is 5.0 The app.js is 'use strict' var express = require('express'); var bodyParser =

Take a look at this Schema: let userSchema = new Schema({ email: { type: String, required: true }, password: { type: String, required: true }, books: [{ cover: String, title: String, link: String, requests: { requestingUser: String, bookOffered: String, beingRequested: false } }], ip: String }); What I am trying to do is use findOneAndUpdate to (based on given information) find the correct user, and then find the correct book (from the array of books by given title) And update the requests field (which is another object.) Is this possible to accomplish with only one findOneAndUpdate query ? So