delete

On this page本页内容

Definition定义

delete

The delete command removes documents from a collection. delete命令从集合中删除文档。A single delete command can contain multiple delete specifications. 一个delete命令可以包含多个delete规范。The command cannot operate on capped collections. 该命令无法对封顶集合进行操作。The remove methods provided by the MongoDB drivers use this command internally.MongoDB驱动程序提供的删除方法在内部使用此命令。

The delete command has the following syntax:delete命令语法如下所示：

{
   delete: <collection>,
   deletes: [
      {
        q : <query>,
        limit : <integer>,
        collation: <document>,
        hint: <document|string>,
        comment: <any>
      },
      ...
   ],
   ordered: <boolean>,
   writeConcern: { <write concern> }
}

The command takes the following fields:该命令包含以下字段：

Field字段Type类型Description描述
delete string

The name of the target collection.目标集合的名称。

deletes array

An array of one or more delete statements to perform in the named collection.要在命名集合中执行的一个或多个delete语句的数组。

ordered boolean

Optional. 可选。If true, then when a delete statement fails, return without performing the remaining delete statements. 如果为true，则当delete语句失败时，返回而不执行其余的delete语句。If false, then when a delete statement fails, continue with the remaining delete statements, if any. 如果为false，则当delete语句失败时，继续执行其余的delete语句（如果有）。Defaults to true.默认为true。

writeConcern document

Optional. 可选。A document expressing the write concern of the delete command. 表示delete命令的写关注点的文档。Omit to use the default write concern.忽略使用默认的写关注点。

Do not explicitly set the write concern for the operation if run in a transaction. 如果在事务中运行，请不要显式设置操作的写入关注点。To use write concern with transactions, see Transactions and Write Concern.要将写关注点用于事务，请参阅事务和写关注点。

comment any

Optional.可选。A user-provided comment to attach to this command. 用户提供了要附加到此命令的注释。Once set, this comment appears alongside records of this command in the following locations:设置后，此注释将与此命令的记录一起出现在以下位置：

A comment can be any valid BSON type (string, integer, object, array, etc).注释可以是任何有效的BSON类型（字符串、整数、对象、数组等）。

New in version 4.4.版本4.4中的新功能。

Each element of the deletes array contains the following fields:deletes数组的每个元素都包含以下字段：

Field字段Type类型Description描述
q document

The query that matches documents to delete.匹配要删除的文档的查询。

limit integer

The number of matching documents to delete. 要删除的匹配文档数。Specify either a 0 to delete all matching documents or 1 to delete a single document.指定0以删除所有匹配的文档，或指定1以删除单个文档。

collation document

Optional.可选。

Specifies the collation to use for the operation.指定要用于该操作的排序规则。

Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks.排序规则允许用户为字符串比较指定特定于语言的规则，例如字母大小写和重音符号的规则。

The collation option has the following syntax:collaction选项语法如下所示：

collation: {
   locale: <string>,
   caseLevel: <boolean>,
   caseFirst: <string>,
   strength: <int>,
   numericOrdering: <boolean>,
   alternate: <string>,
   maxVariable: <string>,
   backwards: <boolean>
}

When specifying collation, the locale field is mandatory; all other collation fields are optional. 指定排序规则时，locale字段是必需的；所有其他排序规则字段都是可选的。For descriptions of the fields, see Collation Document.有关这些字段的描述，请参阅排序规则文档。

If the collation is unspecified but the collection has a default collation (see db.createCollection()), the operation uses the collation specified for the collection.如果未指定排序规则，但集合具有默认排序规则（请参见db.createCollection()），则操作将使用为集合指定的排序规则。

If no collation is specified for the collection or for the operations, MongoDB uses the simple binary comparison used in prior versions for string comparisons.如果没有为集合或操作指定排序规则，MongoDB将使用以前版本中用于字符串比较的简单二进制比较。

You cannot specify multiple collations for an operation. 不能为一个操作指定多个排序规则。For example, you cannot specify different collations per field, or if performing a find with a sort, you cannot use one collation for the find and another for the sort.例如，不能为每个字段指定不同的排序规则，或者如果使用排序执行查找，则不能对查找使用一种排序规则，对排序使用另一种排序规则。

New in version 3.4.版本3.4中的新功能。

hint Document or string

Optional. 可选。A document or string that specifies the index to use to support the query predicate.指定用于支持查询谓词的索引的文档或字符串。

The option can take an index specification document or the index name string.该选项可以采用索引规范文档或索引名称字符串。

If you specify an index that does not exist, the operation errors.如果指定的索引不存在，则操作将出错。

For an example, see Specify hint for Delete Operations.有关示例，请参阅指定删除操作提示。

New in version 4.4.版本4.4中的新功能。

Returns:返回：A document that contains the status of the operation. 包含操作状态的文档。See Output for details.有关详细信息，请参阅输出。

Behavior行为

Sharded Collections碎片集合

All delete operations for a sharded collection that specify the limit: 1 option must include the shard key or the _id field in the query specification. 指定limit:1选项的分片集合的所有delete操作必须在查询规范中包含分片键或_id字段。delete operations specifying limit: 1 in a sharded collection which do not contain either the shard key or the _id field return an error.在不包含分片键或_id字段的分片集合中，指定limit:1的delete操作将返回错误。

Limits限制

The total size of all the queries (i.e. the q field values) in the deletes array must be less than or equal to the maximum BSON document size.deletes数组中所有查询的总大小（即q字段值）必须小于或等于maximum BSON document size。

The total number of delete documents in the deletes array must be less than or equal to the maximum bulk size.deletes数组中的delete文档总数必须小于或等于maximum bulk size。

Transactions事务

delete can be used inside multi-document transactions.删除可以在多文档事务中使用。

Do not explicitly set the write concern for the operation if run in a transaction. 如果在事务中运行，请不要显式设置操作的写入关注点。To use write concern with transactions, see Transactions and Write Concern.要将写关注点用于事务，请参阅事务和写关注点。

Important

In most cases, multi-document transaction incurs a greater performance cost over single document writes, and the availability of multi-document transactions should not be a replacement for effective schema design. 在大多数情况下，与单文档写入相比，多文档事务会带来更大的性能成本，而多文档事务的可用性不应取代有效的模式设计。For many scenarios, the denormalized data model (embedded documents and arrays) will continue to be optimal for your data and use cases. 对于许多场景，非规范化数据模型（嵌入式文档和数组）将继续适合您的数据和用例。That is, for many scenarios, modeling your data appropriately will minimize the need for multi-document transactions.也就是说，对于许多场景，适当地建模数据将最大限度地减少对多文档事务的需求。

For additional transactions usage considerations (such as runtime limit and oplog size limit), see also Production Considerations.有关其他事务使用注意事项（如运行时限制和oplog大小限制），请参阅生产注意事项。

Examples示例

Limit the Number of Documents Deleted限制删除的文档数量

The following example deletes from the orders collection one document that has the status equal to D by specifying the limit of 1:以下示例通过指定limit为1，从orders集合中删除一个状态等于D的文档：

db.runCommand(
   {
      delete: "orders",
      deletes: [ { q: { status: "D" }, limit: 1 } ]
   }
)

The returned document shows that the command deleted 1 document. 返回的文档显示命令删除了1个文档。See Output for details.有关详细信息，请参阅输出。

{ "ok" : 1, "n" : 1 }

Note

All delete operations for a sharded collection that specify the limit: 1 option must include the shard key or the _id field in the query specification. 指定limit:1选项的分片集合的所有delete操作必须在查询规范中包含分片键或_id字段。delete operations specifying limit: 1 in a sharded collection which do not contain either the shard key or the _id field return an error.在不包含分片键或_id字段的分片集合中，指定limit:1的delete操作将返回错误。

Delete All Documents That Match a Condition删除所有符合条件的文档

The following example deletes from the orders collection all documents that have the status equal to D by specifying the limit of 0:以下示例通过指定limit为0，从orders集合中删除status等于D的所有文档：

db.runCommand(
   {
      delete: "orders",
      deletes: [ { q: { status: "D" }, limit: 0 } ],
      writeConcern: { w: "majority", wtimeout: 5000 }
   }
)

The returned document shows that the command found and deleted 13 documents. 返回的文档显示命令找到并删除了13个文档。See Output for details.有关详细信息，请参阅输出。

{ "ok" : 1, "n" : 13 }

Delete All Documents from a Collection从集合中删除所有文档

Delete all documents in the orders collection by specifying an empty query condition and a limit of 0:通过指定空查询条件和0限制，删除orders集合中的所有文档：

db.runCommand(
   {
      delete: "orders",
      deletes: [ { q: { }, limit: 0 } ],
      writeConcern: { w: "majority", wtimeout: 5000 }
   }
)

The returned document shows that the command found and deleted 35 documents in total. 返回的文档显示，该命令总共找到并删除了35个文档。See Output for details.有关详细信息，请参阅输出。

{ "ok" : 1, "n" : 35 }

Bulk Delete批量删除

The following example performs multiple delete operations on the orders collection:以下示例对orders集合执行多个删除操作：

db.runCommand(
   {
      delete: "orders",
      deletes: [
         { q: { status: "D" }, limit: 0 },
         { q: { cust_num: 99999, item: "abc123", status: "A" }, limit: 1 }
      ],
      ordered: false,
      writeConcern: { w: 1 }
   }
)

The returned document shows that the command found and deleted 21 documents in total for the two delete statements. 返回的文档显示，对于这两个delete语句，命令总共找到并删除了21个文档。See Output for details.有关详细信息，请参阅输出。

{ "ok" : 1, "n" : 21 }

Specify Collation指定排序规则

New in version 3.4.版本3.4中的新功能。

Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks.排序规则允许用户为字符串比较指定特定于语言的规则，例如字母大小写和重音符号的规则。

A collection myColl has the following documents:集合myColl包含以下文档：

{ _id: 1, category: "café", status: "A" }
{ _id: 2, category: "cafe", status: "a" }
{ _id: 3, category: "cafE", status: "a" }

The following operation includes the collation option:以下操作包括排序规则选项：

db.runCommand({
   delete: "myColl",
   deletes: [
     { q: { category: "cafe", status: "a" }, limit: 0, collation: { locale: "fr", strength: 1 } }
   ]
})

Specify hint for Delete Operations指定删除操作的hint

New in version 4.4.版本4.4中的新功能。

From the mongo shell, create a members collection with the following documents:在mongo shell中，创建包含以下文档的members集合：

db.members.insertMany([
   { "_id" : 1, "member" : "abc123", "status" : "P", "points" :  0,  "misc1" : null, "misc2" : null },
   { "_id" : 2, "member" : "xyz123", "status" : "A", "points" : 60,  "misc1" : "reminder: ping me at 100pts", "misc2" : "Some random comment" },
   { "_id" : 3, "member" : "lmn123", "status" : "P", "points" :  0,  "misc1" : null, "misc2" : null },
   { "_id" : 4, "member" : "pqr123", "status" : "D", "points" : 20,  "misc1" : "Deactivated", "misc2" : null },
   { "_id" : 5, "member" : "ijk123", "status" : "P", "points" :  0,  "misc1" : null, "misc2" : null },
   { "_id" : 6, "member" : "cde123", "status" : "A", "points" : 86,  "misc1" : "reminder: ping me at 100pts", "misc2" : "Some random comment" }
])

Create the following indexes on the collection:在集合上创建以下索引：

db.members.createIndex( { status: 1 } )
db.members.createIndex( { points: 1 } )

The following delete operation explicitly hints to use the index { status: 1 }:以下删除操作明确提示使用索引{status:1}：

db.runCommand({
   delete: "members",
   deletes: [
     { q: { "points": { $lte: 20 }, "status": "P" }, limit: 0, hint: { status: 1 } }
   ]
})

Note

If you specify an index that does not exist, the operation errors.如果指定的索引不存在，则操作将出错。

To see the index used, run explain on the operation:要查看使用的索引，请对操作运行explain：

db.runCommand(
   {
     explain: {
       delete: "members",
       deletes: [
         { q: { "points": { $lte: 20 }, "status": "P" }, limit: 0, hint: { status: 1 } }
       ]
     },
     verbosity: "queryPlanner"
   }
)

Output输出

The returned document contains a subset of the following fields:返回的文档包含以下字段的子集：

delete.ok

The status of the command.命令的状态。

delete.n

The number of documents deleted.删除的文档数。

delete.writeErrors

An array of documents that contains information regarding any error encountered during the delete operation. 一组文档，其中包含有关删除操作期间遇到的任何错误的信息。The writeErrors array contains an error document for each delete statement that errors.writeErrors数组包含每个删除错误语句的错误文档。

Each error document contains the following information:每个错误文档都包含以下信息：

delete.writeErrors.index

An integer that identifies the delete statement in the deletes array, which uses a zero-based index.一个整数，用于标识deletes数组中的delete语句，该数组使用基于零的索引。

delete.writeErrors.code

An integer value identifying the error.标识错误的整数值。

delete.writeErrors.errmsg

A description of the error.对错误的描述。

delete.writeConcernError

Document that describe error related to write concern and contains the fields:描述与写入问题相关的错误的文档，包含以下字段：

delete.writeConcernError.code

An integer value identifying the cause of the write concern error.标识写入问题错误原因的整数值。

delete.writeConcernError.errmsg

A description of the cause of the write concern error.对写入问题错误原因的描述。

delete.writeConcernError.errInfo.writeConcern

New in version 4.4.版本4.4中的新功能。

The write concern object used for the corresponding operation. 用于相应操作的写关注点对象。For information on write concern object fields, see Write Concern Specification.有关写入关注点对象字段的信息，请参阅写入关注点规范。

The write concern object may also contain the following field, indicating the source of the write concern:写关注点对象还可能包含以下字段，指示写关注点的来源：

delete.writeConcernError.errInfo.writeConcern.provenance

A string value indicating where the write concern originated (known as write concern provenance). 一个字符串值，指示写关注点的来源（称为写关注点provenance）。The following table shows the possible values for this field and their significance:下表显示了该字段的可能值及其重要性：

ProvenanceDescription描述
clientSupplied The write concern was specified in the application.应用程序中指定了写入问题。
customDefault The write concern originated from a custom defined default value. 写入问题源于自定义的默认值。See setDefaultRWConcern.请参阅setDefaultRWConcern。
getLastErrorDefaults The write concern originated from the replica set’s settings.getLastErrorDefaults field.写入问题源于副本集的settings.getLastErrorDefaults字段。
implicitDefault The write concern originated from the server in absence of all other write concern specifications.在没有所有其他写关注规范的情况下，写关注源于服务器。

The following is an example document returned for a successful delete command:以下是成功delete命令返回的示例文档：

{ ok: 1, n: 1 }

The following is an example document returned for a delete command that encountered an error:以下是为遇到错误的delete命令返回的示例文档：

{
   "ok" : 1,
   "n" : 0,
   "writeErrors" : [
      {
         "index" : 0,
         "code" : 10101,
         "errmsg" : "can't remove from a capped collection: test.cappedLog"
      }
   ]
}