db.collection.findAndModify()
On this page本页内容
Definition定义
db.collection.findAndModify(document)
- Important
mongosh Method
This page documents a
mongosh
method. This is not the documentation for database commands or language-specific drivers, such as Node.js.For the database command, see the
findAndModify
command.For MongoDB API drivers, refer to the language-specific MongoDB driver documentation.
For the legacy
mongo
shell documentation, refer to the documentation for the corresponding MongoDB Server release:Modifies and returns a single document. By default, the returned document does not include the modifications made on the update. To return the document with the modifications made on the update, use the修改并返回单个文档。默认情况下,返回的文档不包括对更新所做的修改。要返回在更新时进行了修改的文档,请使用new
option.new
选项。Changed in version 5.0.5.0版更改。ThefindAndModify()
method has the following form:findAndModify()
方法的形式如下:db.collection.findAndModify({
query: <document>,
sort: <document>,
remove: <boolean>,
update: <document or aggregation pipeline>, // Changed in MongoDB 4.2
new: <boolean>,
fields: <document>,
upsert: <boolean>,
bypassDocumentValidation: <boolean>,
writeConcern: <document>,
maxTimeMS: <integer>,
collation: <document>,
arrayFilters: [ <filterdocument1>, ... ],
let: <document> // Added in MongoDB 5.0
});Thedb.collection.findAndModify()
method takes a document parameter with the following embedded document fields:db.collection.findAndModify()
方法采用一个具有以下嵌入文档字段的文档参数:Parameter参数Type类型Description描述query
document Optional.可选的。The selection criteria for the modification.修改的选择标准。Thequery
field employs the same query selectors as used in thedb.collection.find()
method.query
字段使用与db.collection.find()
方法中使用的查询选择器相同的查询选择器。Although the query may match multiple documents,尽管查询可能匹配多个文档,但db.collection.findAndModify()
will only select one document to modify.db.collection.findAndModify()
将只选择一个文档进行修改。
If unspecified, defaults to an empty document.如果未指定,则默认为空文档。
Starting in MongoDB 4.2 (and 4.0.12+, 3.6.14+, and 3.4.23+), the operation errors if the query argument is not a document.从MongoDB 4.2(以及4.0.12+、3.6.14+和3.4.23+)开始,如果query
参数不是文档,则操作会出错。sort
document Optional.可选的。Determines which document the operation modifies if the query selects multiple documents.确定如果查询选择多个文档,则操作将修改哪个文档。db.collection.findAndModify()
modifies the first document in the sort order specified by this argument.按照此参数指定的排序顺序修改第一个文档。
Starting in MongoDB 4.2 (and 4.0.12+, 3.6.14+, and 3.4.23+), the operation errors if the sort argument is not a document.从MongoDB 4.2(以及4.0.12+、3.6.14+和3.4.23+)开始,如果sort
参数不是文档,则操作会出错。
MongoDB does not store documents in a collection in a particular order. When sorting on a field which contains duplicate values, documents containing those values may be returned in any order.MongoDB不会按特定顺序将文档存储在集合中。对包含重复值的字段进行排序时,可以按任何顺序返回包含这些值的文档。
If consistent sort order is desired, include at least one field in your sort that contains unique values. The easiest way to guarantee this is to include the如果需要一致的排序顺序,请在排序中至少包含一个包含唯一值的字段。保证这一点的最简单方法是在排序查询中包含_id
field in your sort query._id
字段。
See Sort Consistency for more information.有关详细信息,请参阅排序一致性。remove
boolean Must specify either the必须指定remove
or theupdate
field.remove
或update
字段。Removes the document specified in the删除query
field.query
字段中指定的文档。Set this to将此设置为true
to remove the selected document .true
可删除所选文档。The default is默认值为false
.false
。update
document or array Must specify either the必须指定remove
or theupdate
field.remove
或update
字段。Performs an update of the selected document.对所选文档执行更新。If passed a document with update operator expressions,如果传递了带有更新运算符表达式的文档,db.collection.findAndModify()
performs the specified modification.db.collection.findAndModify()
将执行指定的修改。If passed a replacement document如果传递了替换文档{ <field1>: <value1>, ...}
, thedb.collection.findAndModify()
performs a replacement.{ <field1>: <value1>, ...}
,db.collection.findAndModify()
将执行替换。Starting in MongoDB 4.2, if passed an aggregation pipeline从MongoDB 4.2开始,如果传递了聚合管道[ <stage1>, <stage2>, ... ]
,db.collection.findAndModify()
modifies the document per the pipeline. The pipeline can consist of the following stages:[ <stage1>, <stage2>, ... ]
,db.collection.findAndModify()
会根据管道修改文档。管道可由以下阶段组成:$addFields
and its alias及其别名$set
$project
and its alias及其别名$unset
$replaceRoot
and its alias及其别名$replaceWith
.
new
boolean Optional.可选的。When如果为true
, returns the modified document rather than the original. The default isfalse
.true
,则返回修改后的文档,而不是原始文档。默认值为false
。fields
document Optional.可选的。A subset of fields to return.要返回的字段的子集。Thefields
document specifies an inclusion of a field with1
, as in:fields: { <field1>: 1, <field2>: 1, ... }
.fields
文档指定包含一个带1
的字段,如fields: { <field1>: 1, <field2>: 1, ... }
。
Starting in MongoDB 4.2 (and 4.0.12+, 3.6.14+, and 3.4.23+), the operation errors if the fields argument is not a document.从MongoDB 4.2(以及4.0.12+、3.6.14+和3.4.23+)开始,如果fields
参数不是文档,则操作会出错。
For more information on projection, see有关投影的详细信息,请参阅fields
Projection.fields
投影。upsert
boolean Optional.可选的。Used in conjunction with the与update
field.update
字段一起使用。
When如果为true
,findAndModify()
either:true
,则findAndModify()
将实现:Creates a new document if no documents match the如果没有与query
.query
匹配的文档,则创建新文档。For more details see upsert behavior.有关更多详细信息,请参阅upsert
行为。Updates a single document that matches the更新与query
.query
匹配的单个文档。
To avoid multiple upserts, ensure that the为了避免多个upsert,请确保查询字段的索引是唯一的。query
field(s) are uniquely indexed.See Upsert with Unique Index for an example.有关示例,请参阅具有唯一索引的Upsert。
Defaults to默认为false
, which does not insert a new document when no match is found.false
,在找不到匹配项时不插入新文档。bypassDocumentValidation
boolean Optional.可选的。Enables启用db.collection.findAndModify()
to bypass document validation during the operation.db.collection.findAndModify()
以在操作过程中绕过文档验证。This lets you update documents that do not meet the validation requirements.这样可以更新不符合验证要求的文档。writeConcern
document Optional.可选的。A document expressing the write concern.表示书面关注的文件。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.要在事务中使用写入关注,请参阅事务和写入关注。maxTimeMS
non-negative integer Optional.可选的。
Specifies a time limit in milliseconds.指定以毫秒为单位的时间限制。If you do not specify a value for如果不指定maxTimeMS
, operations will not time out.maxTimeMS
的值,操作将不会超时。A value of值0
explicitly specifies the default unbounded behavior.0
显式指定默认的无边界行为。
MongoDB terminates operations that exceed their allotted time limit using the same mechanism asMongoDB使用与db.killOp()
.db.killOp()
相同的机制终止超过指定时间限制的操作。MongoDB only terminates an operation at one of its designated interrupt points.MongoDB只在其指定的中断点之一终止操作。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:collation
选项具有以下语法: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.例如,不能为每个字段指定不同的排序规则,或者如果使用排序执行查找,则不能为查找使用一个排序规则,为排序使用另一个排序顺序。arrayFilters
array Optional.可选的。An array of filter documents that determine which array elements to modify for an update operation on an array field.一组筛选文档,用于确定要为数组字段的更新操作修改哪些数组元素。
In the update document, use the在更新文档中,使用$[<identifier>]
filtered positional operator to define an identifier, which you then reference in the array filter documents.$[<identifier>]
筛选的位置运算符来定义标识符,然后在数组筛选文档中引用该标识符。You cannot have an array filter document for an identifier if the identifier is not included in the update document.如果标识符未包含在更新文档中,则不能为该标识符设置数组筛选器文档。NoteThe<identifier>
must begin with a lowercase letter and contain only alphanumeric characters.<identifier>
必须以小写字母开头,并且仅包含字母数字字符。You can include the same identifier multiple times in the update document; however, for each distinct identifier (您可以在更新文档中多次包含相同的标识符;但是,对于更新文档中的每个不同标识符($[identifier]
) in the update document, you must specify exactly one corresponding array filter document.$[identifier]
),必须指定一个对应的数组筛选器文档。That is, you cannot specify multiple array filter documents for the same identifier.也就是说,不能为同一标识符指定多个数组筛选器文档。For example, if the update statement includes the identifier例如,如果x
(possibly multiple times), you cannot specify the following forarrayFilters
that includes 2 separate filter documents forx
:update
语句包含标识符x
(可能多次),则不能为arrayFilters
指定以下内容,因为arrayFilters
包含两个单独的x
筛选文档:// INVALID
[
{ "x.a": { $gt: 85 } },
{ "x.b": { $gt: 80 } }
]However, you can specify compound conditions on the same identifier in a single filter document, such as in the following examples:但是,您可以在单个筛选器文档中对同一标识符指定复合条件,例如以下示例:// Example 1
[
{ $or: [{"x.a": {$gt: 85}}, {"x.b": {$gt: 80}}] }
]
// Example 2
[
{ $and: [{"x.a": {$gt: 85}}, {"x.b": {$gt: 80}}] }
]
// Example 3
[
{ "x.a": { $gt: 85 }, "x.b": { $gt: 80 } }
]For examples, see Specify有关示例,请参阅为数组更新操作指定arrayFilters
for an Array Update Operations.arrayFilters
。NotearrayFilters
is not available for updates that use an aggregation pipeline.不可用于使用聚合管道的更新。let
document Optional.可选的。
Specifies a document with a list of variables.指定具有变量列表的文档。This allows you to improve command readability by separating the variables from the query text.这允许您通过将变量与查询文本分离来提高命令的可读性。
The document syntax is:文档语法为:{ <variable_name_1>: <expression_1>,
...,
<variable_name_n>: <expression_n> }The variable is set to the value returned by the expression, and cannot be changed afterwards.变量设置为表达式返回的值,之后不能更改。
To access the value of a variable in the command, use the double dollar sign prefix (要访问命令中变量的值,请使用双美元符号前缀($$
) together with your variable name in the form$$<variable_name>
.$$
)和形式为$$<variable_name>
的变量名。For example:$$targetTotal
.NoteFor a complete example using有关使用let
and variables, see Use Variables inlet
.let
和变量的完整示例,请参阅在let
中使用变量。
New in version 5.0.5.0版新增。
Return Data返回数据
For remove operations, if the query matches a document, 对于删除操作,如果查询与文档匹配,findAndModify()
returns the removed document. findAndModify()
将返回删除的文档。If the query does not match a document to remove, 如果查询与要删除的文档不匹配,findAndModify()
returns null
.findAndModify()
将返回null
。
For update operations, 对于更新操作,findAndModify()
returns one of the following:findAndModify()
返回以下其中一个:
If the如果new
parameter is not set or isfalse
:new
参数未设置或为false
:the pre-modification document if the query matches a document;如果查询与文档匹配,则显示修改前文档;- otherwise,
null
.
If如果new
istrue
:new
为true
:the modified document if the query returns a match;如果查询返回匹配,则显示修改后的文档;the inserted document if如果upsert: true
and no document matches the query;upsert:true
并且没有与查询匹配的文档,则插入的文档;otherwise,否则为null
.null
。
Behavior行为
fields
Projection投影
Language Consistency语言一致性
Starting in MongoDB 4.4, as part of making 从MongoDB 4.4开始,作为使find()
and findAndModify()
projection consistent with aggregation's $project
stage,find()
和findAndModify()
投影与聚合的$project
阶段一致的一部分,
Thefind()
andfindAndModify()
projection can accept aggregation expressions and syntax.find()
和findAndModify()
投影可以接受聚合表达式和语法。MongoDB enforces additional restrictions with regards to projections.MongoDB对投影实施了额外的限制。See Projection Restrictions for details.有关详细信息,请参阅投影限制。
The fields
option takes a document in the following form:fields
选项采用以下形式的文档:
{ field1: <value>, field2: <value> ... }
<field>: <1 or true> | true .true 。 |
<field>: <0 or false> | |
"<field>.$": <1 or true> | $ array projection operator to return the first element that matches the query condition on the array field. $ 数组投影运算符返回与数组字段上的查询条件匹配的第一个元素。true .true 。 |
<field>: <array projection> | $elemMatch , $slice ) to specify the array elements to include.$elemMatch ,$slice )指定要包含的数组元素。 |
<field>: <aggregation expression> |
true or false to indicate the inclusion or exclusion of the field. true 或false ,以指示包含或排除字段。 |
Embedded Field Specification嵌入式现场规范
For fields in an embedded documents, you can specify the field using either:对于嵌入文档中的字段,可以使用以下任一项指定字段:
dot notation点记号法, for example例如"field.nestedfield": <value>
nested form, for example例如,嵌套形式{ field: { nestedfield: <value> } }
(Starting in MongoDB 4.4)(从MongoDB 4.4开始)
_id
Field Projection字段投影
The _id
field is included in the returned documents by default unless you explicitly specify _id: 0
in the projection to suppress the field._id
字段默认包含在返回的文档中,除非您在投影中明确指定_id:0
以取消显示该字段。
Inclusion or Exclusion包含或排除
A projection
cannot contain both include and exclude specifications, with the exception of the _id
field:projection
不能同时包含include和exclude规范,_id
字段除外:
In projections that explicitly include fields, the在显式包含字段的投影中,_id
field is the only field that you can explicitly exclude._id
字段是唯一可以显式排除的字段。In projections that explicitly excludes fields, the在显式排除字段的投影中,_id
field is the only field that you can explicitly include; however, the_id
field is included by default._id
字段是唯一可以明确包含的字段;但是,_id
字段在默认情况下是包含在内的。
For more information on projection, see also:有关投影的更多信息,另请参见:
Upsert with Unique Index使用唯一索引upsert
When using the 当在upsert: true
option with the findOneAndUpdate()
method, and not using a unique index on the query field(s), multiple instances of a findOneAndUpdate()
operation with similar query field(s) could result in duplicate documents being inserted in certain circumstances.findOneAndUpdate()
方法中使用upsert: true
选项,并且不对查询字段使用唯一索引时,具有类似查询字段的findOneAndUpdate()
操作的多个实例可能会导致在某些情况下插入重复的文档。
Consider an example where no document with the name 考虑一个示例,其中不存在名为Andy
exists and multiple clients issue the following command at roughly the same time:Andy
的文档,并且多个客户端大致同时发出以下命令:
db.people.findAndModify(
{
query: { name: "Andy" },
update: { $inc: { score: 1 } },
upsert: true
}
)
If all 如果所有findOneAndUpdate()
operations finish the query phase before any client successfully inserts data, and there is no unique index on the name
field, each findOneAndUpdate()
operation may result in an insert, creating multiple documents with name: Andy
.findOneAndUpdate()
操作都在任何客户端成功插入数据之前完成了查询阶段,并且name
字段上没有唯一索引,则每个findOneAndUpdate()
操作可能会导致插入,从而创建多个name: Andy
的文档。
To ensure that only one such document is created, and the other 为了确保只创建一个这样的文档,而其他findOneAndUpdate()
operations update this new document instead, create a unique index on the name
field. findOneAndUpdate()
操作会更新这个新文档,请在name
字段上创建一个唯一的索引。This guarantees that only one document with 这保证了集合中只允许一个name: Andy
is permitted in the collection.name: Andy
的文档。
With this unique index in place, the multiple 有了这个唯一的索引,多个findOneAndUpdate()
operations now exhibit the following behavior:findOneAndUpdate()
操作现在表现出以下行为:
Exactly one只需执行一次findOneAndUpdate()
operation will successfully insert a new document.findOneAndUpdate()
操作即可成功插入新文档。All other所有其他findOneAndUpdate()
operations will update the newly-inserted document, incrementing thescore
value.findOneAndUpdate()
操作都将更新新插入的文档,从而增加分值。
Sharded Collections分片集合
When using 对分片集合使用findAndModify
against a sharded collection, the query
must contain an equality condition on shard key.findAndModify
时,query
必须包含分片键上的相等条件。
Starting in version 4.4, documents in a sharded collection can be missing the shard key fields. 从4.4版本开始,分片集合中的文档可能会缺少分片键字段。To target a document that is missing the shard key, you can use the 要针对缺少分片键的文档,可以将null
equality match in conjunction with another filter condition (such as on the _id
field). null
相等匹配与另一个筛选条件结合使用(例如在_id
字段上)。For example:例如:
{ _id: <value>, <shardkeyfield>: null } // _id of the document missing shard key
Shard Key Modification分片键修改
Starting in MongoDB 4.2, you can update a document's shard key value unless the shard key field is the immutable 从MongoDB 4.2开始,您可以更新文档的分片键值,除非分片键字段是不可变的_id
field. In MongoDB 4.2 and earlier, a document's shard key field value is immutable._id
字段。在MongoDB 4.2及更早版本中,文档的分片键字段值是不可变的。
Starting in version 4.4, documents in sharded collections can be missing the shard key fields. Take precaution to avoid accidentally removing the shard key when changing a document's shard key value.从4.4版本开始,分片集合中的文档可能会缺少分片键字段。请采取预防措施,避免在更改文档的分片键值时意外删除分片键。
To modify the existing shard key value with 要使用db.collection.findAndModify()
:db.collection.findAndModify()
修改现有的分片键值,请执行以下操作:
You must run on a你必须在mongos
.mongos
上运行。Do not issue the operation directly on the shard.不要直接在分片上发出操作。You must run either in a transaction or as a retryable write.你必须在事务中运行或作为可重试写入运行。You must include an equality filter on the full shard key.您必须在完整分片键上包含一个相等筛选器。
Missing Shard Key缺少分片键
Starting in version 4.4, documents in a sharded collection can be missing the shard key fields. 从4.4版本开始,分片集合中的文档可能会缺少分片键字段。To use 要使用db.collection.findAndModify()
to set the document's missing shard key:db.collection.findAndModify()
设置文档缺少的分片键,请执行以下操作:
You must run on a你必须在mongos
.mongos
上运行。Do not issue the operation directly on the shard.不要直接在分片上发出操作。You must run either in a transaction or as a retryable write if the new shard key value is not你必须在事务中运行或作为可重试写入运行。null
.You must include an equality filter on the full shard key.你必须在完整分片键上包含一个相等筛选器。
Since a missing key value is returned as part of a null equality match, to avoid updating a null-valued key, include additional query conditions (such as on the 由于丢失的键值是作为_id
field) as appropriate.null
相等匹配的一部分返回的,为了避免更新null
值的键,请酌情包括额外的查询条件(例如在_id
字段上)。
See also:另请参阅:
Document Validation文件验证
The db.collection.findAndModify()
method adds support for the bypassDocumentValidation
option, which lets you bypass document validation when inserting or updating documents in a collection with validation rules.db.collection.findAndModify()
方法添加了对bypassDocumentValidation
选项的支持,该选项允许您在使用验证规则插入或更新集合中的文档时绕过文档验证。
Comparisons with the update
Method与update
方法的比较
update
MethodWhen updating a document, 更新文档时,db.collection.findAndModify()
and the updateOne()
method operate differently:db.collection.findAndModify()
和updateOne()
方法的操作方式不同:
If multiple documents match the update criteria, for如果有多个文档符合更新条件,那么对于db.collection.findAndModify()
, you can specify asort
to provide some measure of control on which document to update.db.collection.findAndModify()
,可以指定一个排序来控制要更新的文档。updateOne()
updates the first document that matches.更新第一个匹配的文档。By default,默认情况下,db.collection.findAndModify()
returns the pre-modified version of the document.db.collection.findAndModify()
返回文档的修改前版本。To obtain the updated document, use the要获取更新的文档,请使用new
option.new
选项。TheupdateOne()
method returns aWriteResult()
object that contains the status of the operation.updateOne()
方法返回一个WriteResult()
对象,该对象包含操作的状态。To return the updated document, use the要返回更新后的文档,请使用find()
method. However, other updates may have modified the document between your update and the document retrieval.find()
方法。但是,在您的更新和文档检索之间,其他更新可能已经修改了文档。Also, if the update modified only a single document but multiple documents matched, you will need to use additional logic to identify the updated document.此外,如果更新只修改了一个文档,但匹配了多个文档,则需要使用额外的逻辑来识别更新的文档。
When modifying a single document, both 修改单个文档时,db.collection.findAndModify()
and the updateOne()
method atomically update the document. See Atomicity and Transactions for more details about interactions and order of operations of these methods.db.collection.findAndModify()
和updateOne()
方法都会自动更新文档。有关这些方法的交互和操作顺序的更多详细信息,请参阅原子性和事务。
Transactions事务
db.collection.findAndModify()
can be used inside multi-document transactions.可以在多文档事务中使用。
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.有关其他事务使用注意事项(如运行时限制和操作日志大小限制),请参阅生产注意事项。
Upsert within Transactions事务中的Upsert
Starting in MongoDB 4.4, you can create collections and indexes inside a multi-document transaction if the transaction is not a cross-shard write transaction.从MongoDB 4.4开始,如果多文档事务不是跨分片写入事务,则可以在该事务内创建集合和索引。
Specifically, in MongoDB 4.4 and greater, 具体来说,在MongoDB 4.4及更高版本中,具有db.collection.findAndModify()
with upsert: true
can be run on an existing collection or a non-existing collection. upsert:true
的db.collection.findAndModify()
可以在现有集合或不存在的集合上运行。If run on a non-existing collection, the operation creates the collection.如果在不存在的集合上运行,则该操作将创建该集合。
In MongoDB 4.2 and earlier, the operation must be run on an existing collection.在MongoDB 4.2及更早版本中,操作必须在现有集合上运行。
See also: 另请参阅:
Write Concerns and 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.如果在事务中运行,请不要显式设置操作的写入关注。要在事务中使用写入关注,请参阅事务和写入关注。
Examples实例
Update and Return更新和返回
The following method updates and returns an existing document in the people collection where the document matches the query criteria:以下方法更新并返回人员集合中与查询条件匹配的现有文档:
db.people.findAndModify({
query: { name: "Tom", state: "active", rating: { $gt: 10 } },
sort: { rating: 1 },
update: { $inc: { score: 1 } }
})
This method performs the following actions:此方法执行以下操作:
Thequery
finds a document in thepeople
collection where thename
field has the valueTom
, thestate
field has the valueactive
and therating
field has a valuegreater than
10.query
在people
集合中查找一个文档,其中name
字段的值为Tom
,state
字段的值为active
,rating
字段的值大于10
。Thesort
orders the results of the query in ascending order.sort
按升序排列查询结果。If multiple documents meet the如果多个文档满足query
condition, the method will select for modification the first document as ordered by thissort
.query
条件,则该方法将选择按此sort
的第一个文档进行修改。The update更新会将increments
the value of thescore
field by 1.score
字段的值增加1
。The method returns the original (i.e. pre-modification) document selected for this update:该方法返回为此更新选择的原始(即修改前)文档:{
"_id" : ObjectId("50f1e2c99beb36a0f45c6453"),
"name" : "Tom",
"state" : "active",
"rating" : 100,
"score" : 5
}To return the modified document, add the要返回修改后的文档,请将new:true
option to the method.new:true
选项添加到方法中。If no document matched the如果没有与query
condition, the method returnsnull
.query
条件匹配的文档,则该方法返回null
。
Upsert
The following method includes the 以下方法包括更新操作的upsert: true
option for the update
operation to either update a matching document or, if no matching document exists, create a new document:upsert:true
选项,用于update
匹配的文档,或者如果不存在匹配的文档则创建新文档:
db.people.findAndModify({
query: { name: "Gus", state: "active", rating: 100 },
sort: { rating: 1 },
update: { $inc: { score: 1 } },
upsert: true
})
If the method finds a matching document, the method performs an update.如果该方法找到匹配的文档,则该方法将执行更新。
If the method does not find a matching document, the method creates a new document. Because the method included the 如果该方法找不到匹配的文档,则该方法将创建一个新文档。由于该方法包含sort
option, it returns an empty document { }
as the original (pre-modification) document:sort
选项,因此它返回一个空文档{ }
作为原始(修改前)文档:
{ }
If the method did not include a 如果该方法不包括sort
option, the method returns null
.sort
选项,则该方法将返回null
。
null
Return New Document返回新文档
The following method includes both the 以下方法包括upsert: true
option and the new:true
option. upsert: true
选项和new:true
选项。The method either updates a matching document and returns the updated document or, if no matching document exists, inserts a document and returns the newly inserted document in the 该方法更新匹配的文档并返回更新后的文档,或者,如果不存在匹配的文档,则插入文档并在value
field.value
字段中返回新插入的文档。
In the following example, no document in the 在以下示例中,people
collection matches the query
condition:people
集合中没有与query
条件匹配的文档:
db.people.findAndModify({
query: { name: "Pascal", state: "active", rating: 25 },
sort: { rating: 1 },
update: { $inc: { score: 1 } },
upsert: true,
new: true
})
The method returns the newly inserted document:该方法返回新插入的文档:
{
"_id" : ObjectId("50f49ad6444c11ac2448a5d6"),
"name" : "Pascal",
"rating" : 25,
"score" : 1,
"state" : "active"
}
Sort and Remove排序和删除
By including a 通过在sort
specification on the rating
field, the following example removes from the people
collection a single document with the state
value of active
and the lowest rating
among the matching documents:rating
字段中包含sort
规范,以下示例将从people
集合中删除state
值为active
且在匹配文档中rating
最低的单个文档:
db.people.findAndModify(
{
query: { state: "active" },
sort: { rating: 1 },
remove: true
}
)
The method returns the deleted document:该方法返回已删除的文档:
{
"_id" : ObjectId("52fba867ab5fdca1299674ad"),
"name" : "XYZ123",
"score" : 1,
"state" : "active",
"rating" : 3
}
Specify Collation指定排序规则
Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks.collation
允许用户为字符串比较指定特定于语言的规则,例如大小写和重音标记的规则。
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:以下操作包括collation
选项:
db.myColl.findAndModify({
query: { category: "cafe", status: "a" },
sort: { category: 1 },
update: { $set: { status: "Updated" } },
collation: { locale: "fr", strength: 1 }
});
The operation returns the following document:该操作返回以下文档:
{ "_id" : 1, "category" : "café", "status" : "A" }
Specify arrayFilters
for an Array Update Operations为数组更新操作指定arrayFilters
arrayFilters
for an Array Update OperationsarrayFilters
is not available for updates that use an aggregation pipeline.不可用于使用聚合管道的更新。
Starting in MongoDB 3.6, when updating an array field, you can specify 从MongoDB 3.6开始,在更新数组字段时,可以指定arrayFilters
that determine which array elements to update.arrayFilters
来确定要更新的数组元素。
Update Elements Match arrayFilters
Criteria更新元素匹配arrayFilters
条件
arrayFilters
CriteriaarrayFilters
is not available for updates that use an aggregation pipeline.不可用于使用聚合管道的更新。
Create a collection 使用以下文档创建students
with the following documents:students
集合:
db.students.insertMany( [
{ "_id" : 1, "grades" : [ 95, 92, 90 ] },
{ "_id" : 2, "grades" : [ 98, 100, 102 ] },
{ "_id" : 3, "grades" : [ 95, 110, 100 ] }
] )
To modify all elements that are greater than or equal to 要修改100
in the grades
array, use the filtered positional operator $[<identifier>]
with the arrayFilters
option in the db.collection.findAndModify()
method:grades
数组中所有大于或等于100
的元素,请在db.collection.findAndModify()
方法中使用筛选后的位置运算符$[<identifier>]
和arrayFilters
选项:
db.students.findAndModify({
query: { grades: { $gte: 100 } },
update: { $set: { "grades.$[element]" : 100 } },
arrayFilters: [ { "element": { $gte: 100 } } ]
})
The operation updates the 该操作会更新单个文档的grades
field for a single document, and after the operation, the collection has the following documents:grades
字段,操作完成后,集合将具有以下文档:
{ "_id" : 1, "grades" : [ 95, 92, 90 ] }
{ "_id" : 2, "grades" : [ 98, 100, 100 ] }
{ "_id" : 3, "grades" : [ 95, 110, 100 ] }
Update Specific Elements of an Array of Documents更新文档数组的特定元素
arrayFilters
is not available for updates that use an aggregation pipeline.不可用于使用聚合管道的更新。
Create a collection 使用以下文档创建集合students2
with the following documents:students2
:
db.students2.insertMany( [
{
"_id" : 1,
"grades" : [
{ "grade" : 80, "mean" : 75, "std" : 6 },
{ "grade" : 85, "mean" : 90, "std" : 4 },
{ "grade" : 85, "mean" : 85, "std" : 6 }
]
},
{
"_id" : 2,
"grades" : [
{ "grade" : 90, "mean" : 75, "std" : 6 },
{ "grade" : 87, "mean" : 90, "std" : 3 },
{ "grade" : 85, "mean" : 85, "std" : 4 }
]
}
] )
The following operation finds a document where the 以下操作查找_id
field equals 1
and uses the filtered positional operator $[<identifier>]
with the arrayFilters
to modify the mean
for all elements in the grades
array where the grade is greater than or equal to 85
._id
字段等于1
的文档,并将筛选后的位置运算符$[<identifier>]
与arrayFilters
一起使用,以修改grades
数组中grade
大于或等于85
的所有元素的mean
(平均值)。
db.students2.findAndModify({
query: { _id : 1 },
update: { $set: { "grades.$[elem].mean" : 100 } },
arrayFilters: [ { "elem.grade": { $gte: 85 } } ]
})
The operation updates the 该操作会更新单个文档的grades
field for a single document, and after the operation, the collection has the following documents:grades
字段,操作完成后,集合将具有以下文档:
{
"_id" : 1,
"grades" : [
{ "grade" : 80, "mean" : 75, "std" : 6 },
{ "grade" : 85, "mean" : 100, "std" : 4 },
{ "grade" : 85, "mean" : 100, "std" : 6 }
]
}
{
"_id" : 2,
"grades" : [
{ "grade" : 90, "mean" : 75, "std" : 6 },
{ "grade" : 87, "mean" : 90, "std" : 3 },
{ "grade" : 85, "mean" : 85, "std" : 4 }
]
}
Use an Aggregation Pipeline for Updates使用聚合管道进行更新
Starting in MongoDB 4.2, 从MongoDB 4.2开始,db.collection.findAndModify()
can accept an aggregation pipeline for the update. The pipeline can consist of the following stages:db.collection.findAndModify()
可以接受更新的聚合管道。管道可由以下阶段组成:
$addFields
and its alias及其别名$set
$project
and its alias及其别名$unset
$replaceRoot
and its alias及其别名$replaceWith
.
Using the aggregation pipeline allows for a more expressive update statement, such as expressing conditional updates based on current field values or updating one field using the value of another field(s).使用聚合管道可以实现更具表达力的更新语句,例如基于当前字段值表达条件更新,或者使用另一个字段的值更新一个字段。
For example, create a collection 例如,使用以下文档创建集合students2
with the following documents:students2
:
db.students2.insertMany( [
{
"_id" : 1,
"grades" : [
{ "grade" : 80, "mean" : 75, "std" : 6 },
{ "grade" : 85, "mean" : 90, "std" : 4 },
{ "grade" : 85, "mean" : 85, "std" : 6 }
]
},
{
"_id" : 2,
"grades" : [
{ "grade" : 90, "mean" : 75, "std" : 6 },
{ "grade" : 87, "mean" : 90, "std" : 3 },
{ "grade" : 85, "mean" : 85, "std" : 4 }
]
}
] )
The following operation finds a document where the 以下操作查找_id
field equals 1
and uses an aggregation pipeline to calculate a new field total
from the grades
field:_id
字段等于1
的文档,并使用聚合管道从grades
字段计算新的字段total
:
db.students2.findAndModify( {
query: { "_id" : 1 },
update: [ { $set: { "total" : { $sum: "$grades.grade" } } } ], // The $set stage is an alias for ``$addFields`` stage
new: true
} )
The operation returns the updated document:该操作返回更新后的文档:
{
"_id" : 1,
"grades" : [ { "grade" : 80, "mean" : 75, "std" : 6 }, { "grade" : 85, "mean" : 90, "std" : 4 }, { "grade" : 85, "mean" : 85, "std" : 6 } ],
"total" : 250
}
Use Variables in let
在let
中使用变量
let
New in version 5.0. 5.0版新增。
To define variables that you can access elsewhere in the command, use the let option.要定义可以在命令的其他地方访问的变量,请使用let
选项。
Create a collection 创建一个集合cakeFlavors
:cakeFlavors
:
db.cakeFlavors.insertMany( [
{ _id: 1, flavor: "chocolate" },
{ _id: 2, flavor: "strawberry" },
{ _id: 3, flavor: "cherry" }
] )
The following example defines a 以下示例在targetFlavor
variable in let
and uses the variable to change the cake flavor from cherry to orange:let
中定义了targetFlavor
变量,并使用该变量将蛋糕口味从樱桃改为橙色:
db.cakeFlavors.findAndModify( {
query: {
$expr: { $eq: [ "$flavor", "$$targetFlavor" ] }
},
update: { flavor: "orange" },
let: { targetFlavor: "cherry" }
} )
User Roles and Document Updates用户角色和文档更新
Starting in MongoDB 7.0, you can use the new 从MongoDB 7.0开始,您可以使用新的USER_ROLES
system variable to return user roles.USER_ROLES
系统变量来返回用户角色。
The example in this section shows updates to fields in a collection containing medical information. 本节中的示例显示了对包含医疗信息的集合中的字段的更新。The example reads the current user roles from the 此示例从USER_ROLES
system variable and only performs the updates if the user has a specific role.USER_ROLES
系统变量中读取当前用户角色,并且仅当用户具有特定角色时才执行更新。
To use a system variable, add 要使用系统变量,请在变量名的开头添加$$
to the start of the variable name. Specify the USER_ROLES
system variable as $$USER_ROLES
.$$
。将USER_ROLES
系统变量指定为$$USER_ROLES
。
The example creates these users:该示例创建了以下用户:
具有James
with aBilling
role.Billing
角色的James
具有Michelle
with aProvider
role.Provider
角色的Michelle
Perform the following steps to create the roles, users, and collection:执行以下步骤以创建角色、用户和集合:
Create the roles创建角色
Create roles named 创建具有所需权限和资源的名为Billing
and Provider
with the required privileges and resources.Billing
和Provider
的角色。
Run:运行:
db.createRole( { role: "Billing", privileges: [ { resource: { db: "test",
collection: "medicalView" }, actions: [ "find" ] } ], roles: [ ] } )
db.createRole( { role: "Provider", privileges: [ { resource: { db: "test",
collection: "medicalView" }, actions: [ "find" ] } ], roles: [ ] } )
Log in as as 以Michelle
, who has the Provider
role, and perform an update:Michelle
的身份登录,Michelle
具有Provider
角色,并执行更新:
Perform update执行更新
Run:运行:
//Attempt to find and modify document尝试查找和修改文档
db.medical.findAndModify( {
query:
{ $and: [
{
//Only update the document for Mary Smith仅为Mary Smith更新文档
patientName: { $eq: "Mary Smith" }
},
{
//User must have the Provider role to perform the update用户必须具有提供Provider才能执行更新
$expr: { $ne: [ {
$setIntersection: [ [ "Provider" ], "$$USER_ROLES.role" ]
}, [] ] }
}
]
},
//Update document更新文档
update: {
patientName: "Mary Smith",
diagnosisCode: "ACH 03",
creditCard: "6541-7534-9637-3456"
}
} )
The previous example uses 上一个示例使用$setIntersection
to return documents where the intersection between the "Provider"
string and the user roles from $$USER_ROLES.role
is not empty. $setIntersection
返回"Provider"
字符串与$$USER_ROLES.role
中的用户角色之间的交集不为空的文档。Michelle
has the Provider
role, so the update is performed.Michelle
具有Provider
角色,因此执行更新。
Next, log in as as 接下来,以James
, who does not have the Provider
role, and attempt to perform the same update:James
的身份登录,James
没有Provider
角色,并尝试执行相同的更新:
Attempt to perform update尝试执行更新
Run:运行:
//Attempt to find and modify document尝试查找和修改文档
db.medical.findAndModify( {
query:
{ $and: [
{
//Only update the document for Mary Smith仅为Mary Smith更新文档
patientName: { $eq: "Mary Smith" }
},
{
//User must have the Provider role to perform the update用户必须具有Provider角色才能执行更新
$expr: { $ne: [ {
$setIntersection: [ [ "Provider" ], "$$USER_ROLES.role" ]
}, [] ] }
}
]
},
//Update document更新文档
update: {
patientName: "Mary Smith",
diagnosisCode: "ACH 03",
creditCard: "6541-7534-9637-3456"
}
} )
The previous example does not update any documents.上一个示例不更新任何文档。