summaryrefslogtreecommitdiff
path: root/src/mongo/db/ops/parsed_delete.cpp
diff options
context:
space:
mode:
authorTess Avitabile <tess.avitabile@mongodb.com>2016-05-09 14:38:42 -0400
committerTess Avitabile <tess.avitabile@mongodb.com>2016-05-16 16:02:00 -0400
commitf007a7b91835b34c06401191cc879f5343023a4b (patch)
treeae30e8a570a9c006e9efc8b73f5e85976f1e04a2 /src/mongo/db/ops/parsed_delete.cpp
parentfee016c605c3914c665d6643f66b3685643206ea (diff)
downloadmongo-f007a7b91835b34c06401191cc879f5343023a4b.tar.gz
SERVER-23610 CanonicalQuery should own a CollatorInterface
Diffstat (limited to 'src/mongo/db/ops/parsed_delete.cpp')
-rw-r--r--src/mongo/db/ops/parsed_delete.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mongo/db/ops/parsed_delete.cpp b/src/mongo/db/ops/parsed_delete.cpp
index a47c3ad0ad1..4e027390a79 100644
--- a/src/mongo/db/ops/parsed_delete.cpp
+++ b/src/mongo/db/ops/parsed_delete.cpp
@@ -80,6 +80,7 @@ Status ParsedDelete::parseQueryToCQ() {
auto lpq = stdx::make_unique<LiteParsedQuery>(_request->getNamespaceString());
lpq->setFilter(_request->getQuery());
lpq->setSort(_request->getSort());
+ lpq->setCollation(_request->getCollation());
lpq->setExplain(_request->isExplain());
// Limit should only used for the findAndModify command when a sort is specified. If a sort
@@ -88,7 +89,6 @@ Status ParsedDelete::parseQueryToCQ() {
// deleted out from under it, but a limit could inhibit that and give an EOF when the delete
// has not actually deleted a document. This behavior is fine for findAndModify, but should
// not apply to deletes in general.
- // TODO SERVER-23473: Pass the collation to canonicalize().
if (!_request->isMulti() && !_request->getSort().isEmpty()) {
lpq->setLimit(1);
}