-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:v2.4.6 Linux 64 bit
*Location*: http://docs.mongodb.org/manual/core/index-sparse/
*User-Agent*: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 IKDhPmJcdw
*Referrer*: http://docs.mongodb.org/manual/core/indexes/
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: core/index-sparse
v2.4.6 Linux 64 bit *Location*: http://docs.mongodb.org/manual/core/index-sparse/ *User-Agent*: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 IKDhPmJcdw *Referrer*: http://docs.mongodb.org/manual/core/indexes/ *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: core/index-sparse
Your example of the unique sparse index is wrong. Why shouldn't one be able to insert the last two records? Unique index is on score and not on userid!
Here my console output to prove it:
mongos> db.scores.find()
mongos> db.scores.ensureIndex(
,
{ sparse: true, unique: true } )
mongos> db.scores.insert(
)
mongos> db.scores.insert(
)
mongos> db.scores.insert(
)
mongos> db.scores.insert(
)
mongos> db.scores.find()
mongos> db.scores.insert(
{ "userid": "PWWfO8lFs1", "score": "82" } )
mongos> db.scores.insert(
)
mongos> db.scores.find()
mongos>