Support duplicate validation on index: { unique: true} }

[ydaniv]

For now Mockgoose requires setting unique: true explicitly on the field.
mongod will throw 11000 error for index: { unique: true} } but Mockgoose ignores it and test relying on this error occurring will fail.

[ydaniv]

Managed to hack this with the following:

my_model.schema.path('field').options.unique = true;

[mccormicka]

@ydaniv can you supply an example?

[mccormicka]

@ydaniv added a test for this
c8ecfbb

Is that what you meant?

[ydaniv]

@mccormicka thanks for the response!

I think it's not quite what I meant.
What I expect is that mockgoose will throw a "duplicate key" validation error for a Schema with a field that has index: { unique: true }, which implicitly also means (if I'm not mistaken) that that field will also become unique: true.

In any case, mongod does raise a "duplicate key" error, so I expect it to also be supported for consistency.

I think currently it's not supported in mockgoose, so it requires also extra implementation.

Would you like me to try and tackle this?

[mccormicka]

Hi @ydaniv can you add a test case? Then I would be able to understand the issue a bit better.

Thanks

[mccormicka]

@ydaniv I merged your branch but these tests also fail when I run them against a real MongoDB instance. Do you see the same if you run it against mongodb without mockgoose?

[ydaniv]

@mccormicka yes, for me they also fail. The error I see in the mongod console is not propagated for some reason through Mongoose. Did you you notice that error in the console?
However, in a plain Mongoose-over-MongoDB app I do get an error.
Something in the config here is different but I can't say what it is.

[nivthefox]

Just as a note, compound uniques are also not being caught by mockgoose.

Example:
MySchema.index({name: 1, server: 1}, {unique: true});

I can create two instances of MySchema model with the same name/server property.

[jaseeey]

Has anyone had any luck with this issue? I'm finding that my unique indexes are being ignored when performing an update() using Mockgoose. The only way around this is using a save() which does throw a duplicate key error, however update() simply updates and allows a duplicate to exist whilst the actual MongoDB throws an error.

[winfinit]

5.0 honors indexes

[jaseeey]

Thank you for following this up, has this been applied to the latest 5.0rc?