WriteResult()
On this page
Definition
WriteResult()
A wrapper that contains the result status of
mongosh
write methods.Note
db.collection.insert()
anddb.collection.update()
are deprecated.The results returned by the replacement methods have a different format. For output similar to
WriteResult()
, consider usingdb.collection.bulkWrite()
.
Properties
The WriteResult()
has the following properties:
WriteResult.nInserted
The number of documents inserted, excluding
upserted
documents. SeeWriteResult.nUpserted
for the number of documents inserted through an upsert.
WriteResult.nMatched
The number of documents selected for update. If the update operation results in no change to the document, e.g.
$set
expression updates the value to the current value,nMatched
can be greater thannModified
.
WriteResult.nModified
The number of existing documents updated. If the update/replacement operation results in no change to the document, such as setting the value of the field to its current value,
nModified
can be less thannMatched
.
WriteResult.nUpserted
The number of documents inserted by an upsert.
WriteResult._id
The
_id
of the document inserted by anupsert
. Returned only if anupsert
results in an insert.
WriteResult.writeError
A document that contains information regarding any error, excluding write concern errors, encountered during the write operation.
WriteResult.writeConcernError
Document describing errors that relate to the write concern.
Changed in version 7.1: When
WriteResult()
is received frommongos
, write concern errors are always reported, even when one or more write errors occur.In previous releases, the occurrence of write errors could cause the
WriteResult()
to not report write concern errors.WriteResult.writeConcernError.code
An integer value identifying the cause of the write concern error.
WriteResult.writeConcernError.errInfo.writeConcern
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:
WriteResult.writeConcernError.errInfo.writeConcern.provenance
A string value indicating where the write concern originated (known as write concern
provenance
). The following table shows the possible values for this field and their significance:ProvenanceDescriptionclientSupplied
The write concern was specified in the application.customDefault
The write concern originated from a custom defined default value. SeesetDefaultRWConcern
.getLastErrorDefaults
The write concern originated from the replica set'ssettings.getLastErrorDefaults
field.implicitDefault
The write concern originated from the server in absence of all other write concern specifications.