1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
// Cannot implicitly shard accessed collections because of following errmsg: A single
// update/delete on a sharded collection must contain an exact match on _id or contain the shard
// key.
// @tags: [assumes_unsharded_collection]
t = db.jstests_pull;
t.drop();
t.save({a: [1, 2, 3]});
t.update({}, {$pull: {a: 2}});
t.update({}, {$pull: {a: 6}});
assert.eq([1, 3], t.findOne().a);
t.drop();
t.save({a: [1, 2, 3]});
t.update({}, {$pull: {a: 2}});
t.update({}, {$pull: {a: 2}});
assert.eq([1, 3], t.findOne().a);
t.drop();
t.save({a: [2]});
t.update({}, {$pull: {a: 2}});
t.update({}, {$pull: {a: 6}});
assert.eq([], t.findOne().a);
// SERVER-6047: $pull creates empty nested docs for dotted fields
// that don't exist.
t.drop();
t.save({m: 1});
t.update({m: 1}, {$pull: {'a.b': [1]}});
assert(('a' in t.findOne()) == false);
// Non-obvious bit: the implementation of non-in-place update
// might do different things depending on whether the "new" field
// comes before or after existing fields in the document.
// So for now it's worth testing that too. Sorry, future; blame the past.
t.update({m: 1}, {$pull: {'x.y': [1]}});
assert(('z' in t.findOne()) == false);
// End SERVER-6047
|
