Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Duplicate
-
1.8.0-rc1
-
None
-
None
-
Windows 7, single instance, no shards
-
ALL
Description
db.foo.ensureIndex(
{a : 1});
db.foo.save(
);
db.foo.save(
);
db.foo.ensureIndex(
{a : 1},
{name:'uniquea', unique:true});
db.foo.getIndexes() shows that 'uniquea' has not been created. While we should be checking to avoid creating exact duplicate indexes, my attempt to create a new unique index should succeed, because there isn't already a unique one. I might be doing this in preparation for replacing the (non-unique) 'a_1' index with 'uniquea'.
Attachments
Issue Links
- duplicates
-
SERVER-2618 Attempting to create a new index that already exists with diff option fails silently
-
- Closed
-