Error With Status of 0

[VARG0S]

Hello,
I am not sure what is causing this, but I have always used the status property of the Object returned from MERS to determine whether an error has occurred. I am getting an error from MongoDB about a duplicate id, (I know the this error isn't a MERS issues), but I was surprised when the object comes back from MERS with an "error" property and the status was 0. I was just curious if you had any insight into this, I know I am probably missing something obvious, but I am losing track of the code during this snippet from route.js

router.post(base + '/:type', function (req, res) {
        var Model = m(req);
        new Model(clean(req.body)).save(run(res));
    });

Thanks for any insight you may be able to provide

[jspears]

That isn't good, I'll write a test and try to get to the bottom of it. Thanks for the info!

[jspears]

I believe that is happening because the validation happens within mongo, not mongoose where most validation happens. However, I can not seem to reproduce the error.... be great if you could share part of a schema that this happens with.

[VARG0S]

I think you are exactly right. I ran across this when I changed the name of an indexed unique field in my mongoose schema. So I had the first schema and then I changed it to the second listed below. When I went to insert a new record using the new schema, it would fail because Mongo was still looking for a "Name" index in addition to the newly created "usertype_name" index, but I was only sending the required "usertype_name" field and "Name" wasn't being sent and consequently wasn't satisfying the mongo rules.

Original:

var UserTypeSchema = new Schema({
        Name: {type: String, index: { unique: true } },
        Description: {type: String }
    });

Modified:

var UserTypeSchema = new Schema({
        usertype_name: {type: String, index: { unique: true } },
        usertype_description: {type: String }
    });