Details
Description
This will set the fields specified in $setOnInsert:
{<fields>}if the update results in an insert. It does nothing if any existing documents are updated.
Issue Links
- depends on
-
SERVER-6399
Refactor update() code
-
- Closed
-
- is depended on by
-
DOCS-875
Add new $setOnInsert documentation
-
- Closed
-
- is duplicated by
-
SERVER-453
$iset - set fields only on insert when upserting
-
- Closed
-
-
SERVER-3440
Add $setOnInsert command
-
- Closed
-
-
SERVER-4900
$ifnotpresent
-
- Closed
-
- is related to
-
SERVER-7894
A $setOnChange command would be very helpful
-
- Closed
-
- related to
-
CSHARP-684
Add new features to Update builder for server 2.4
-
- Closed
-
Activity
Author:
{u'date': u'2012-12-12T16:46:47Z', u'email': u'alerner@10gen.com', u'name': u'Alberto Lerner'}Message: SERVER-340 Created a $setOnInsert update operator.
Branch: master
https://github.com/mongodb/mongo/commit/ac3f20c6dcb8aeaa9ae7182816ab1dc4f15619f5
Already discussed documentation needs with Sam.
The implementation in 2.3.2 is actually what "$setIfAbsent" should be and not the correct behavior of $setOnInsert.
Author:
{u'date': u'2013-02-07T21:53:24Z', u'email': u'alerner@10gen.com', u'name': u'Alberto Lerner'}Message: SERVER-340 $setOnInsert should be a no-op in an update.
Branch: master
https://github.com/mongodb/mongo/commit/52858af695150e71ca17f06e10c07419d54af42b
@Scott Nichol +1
suggest clarifying the description... "adds new properties only if it doesn't exist yet." Does this mean that each property is added only if that property does not exist, and that this decision is made independently for each key in $add's value? (that's what I think you mean) Or that they all get added only if all of them do not exist?