On this page本页内容
db.collection.deleteMany()
This is a mongosh
method. This is not the documentation for Node.js
or other programming language specific driver methods.
In most cases, mongosh
methods work the same way as the legacy mongo
shell methods. However, some legacy methods are unavailable in mongosh
.
For the legacy mongo
shell documentation, refer to the documentation for the corresponding MongoDB Server release:
For MongoDB API drivers, refer to the language specific MongoDB driver documentation.
Removes all documents that match the 从集合中删除与filter
from a collection.filter
匹配的所有文档。
db.collection.deleteMany( <filter>, { writeConcern: <document>, collation: <document> } )
filter | document |
|
writeConcern | document |
|
collation | document |
collation: { locale: <string>, caseLevel: <boolean>, caseFirst: <string>, strength: <int>, numericOrdering: <boolean>, alternate: <string>, maxVariable: <string>, backwards: <boolean> }
|
hint | document |
|
|
如果在封顶集合上使用db.collection.deleteMany()
throws a WriteError
exception if used on a capped collection. db.collection.deleteMany()
,则会引发WriteError
异常。To remove all documents from a capped collection, use 要从封顶集合中删除所有文档,请使用db.collection.drop()
.db.collection.drop()
。
如果在时间序列集合上使用db.collection.deleteMany()
throws a WriteError
exception if used on a time series collection. db.collection.deleteMany()
,则会引发WriteError
异常。To remove all documents from a time series collection, use 要从时间序列集合中删除所有文档,请使用db.collection.drop()
.db.collection.drop()
。
To delete a single document, use 要删除单个文档,请改用db.collection.deleteOne()
instead.db.collection.deleteOne()
。
Alternatively, use a field that is a part of a unique index such as 或者,使用作为唯一索引一部分的字段,例如_id
._id
。
db.collection.deleteMany()
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.要对事务使用写关注点,请参阅事务和写关注点。
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大小限制),请参阅生产注意事项。
The orders
collection has documents with the following structure:orders
集合具有以下结构的文档:
{ _id: ObjectId("563237a41a4d68582c2509da"), stock: "Brent Crude Futures", qty: 250, type: "buy-limit", limit: 48.90, creationts: ISODate("2015-11-01T12:30:15Z"), expiryts: ISODate("2015-11-01T12:35:15Z"), client: "Crude Traders Inc." }
The following operation deletes all documents where 以下操作删除client : "Crude Traders Inc."
:client : "Crude Traders Inc."
的所有文件:
try { db.orders.deleteMany( { "client" : "Crude Traders Inc." } ); } catch (e) { print (e); }
The operation returns:操作返回:
{ "acknowledged" : true, "deletedCount" : 10 }
The following operation deletes all documents where 以下操作删除stock : "Brent Crude Futures"
and limit
is greater than 48.88
:stock : "Brent Crude Futures"
且limit
大于48.88
的所有文件:
try { db.orders.deleteMany( { "stock" : "Brent Crude Futures", "limit" : { $gt : 48.88 } } ); } catch (e) { print (e); }
The operation returns:操作返回:
{ "acknowledged" : true, "deletedCount" : 8 }
deleteMany()
Given a three member replica set, the following operation specifies a 给定一个三成员副本集,以下操作指定w
of majority
and wtimeout
of 100
:w
为"majority"
,wtimeout
为100
:
try { db.orders.deleteMany( { "client" : "Crude Traders Inc." }, { w : "majority", wtimeout : 100 } ); } catch (e) { print (e); }
If the acknowledgement takes longer than the 如果确认花费的时间超过wtimeout
limit, the following exception is thrown:wtimeout
限制,将引发以下异常:
WriteConcernError({ "code" : 64, "errmsg" : "waiting for replication timed out", "errInfo" : { "wtimeout" : true, "writeConcern" : { // Added in MongoDB 4.4 "w" : "majority", "wtimeout" : 100, "provenance" : "getLastErrorDefaults" } } })
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.myColl.deleteMany( { category: "cafe", status: "A" }, { collation: { locale: "fr", strength: 1 } } )
hint
for Delete Operationshint
New in version 4.4.在版本4.4中新增。
In 在mongosh
, create a members
collection with the following documents:mongosh
中,使用以下文档创建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.members.deleteMany( { "points": { $lte: 20 }, "status": "P" }, { hint: { status: 1 } } )
If you specify an index that does not exist, the operation errors.如果指定的索引不存在,则操作会出错。
The delete command returns the following:delete
命令返回以下内容:
{ "acknowledged" : true, "deletedCount" : 3 }
To view the indexes used, you can use the 要查看使用的索引,可以使用$indexStats
pipeline:$indexStats
管道:
db.members.aggregate( [ { $indexStats: { } }, { $sort: { name: 1 } } ] )
The accesses.ops
field in the $indexStats
output indicates the number of operations that used the index.$indexStats
输出中的accesses.ops
字段指示使用索引的操作数。