On this page
Specifies the level of write concern for confirming the success of previous write operation issued over the same connection and returns the
error stringfor that operation.
db.getLastError(), clients must issue the
db.getLastError()on the same connection as the write operation they wish to confirm.
Changed in version 2.6: A new protocol for write operations integrates write concerns with the write operations, eliminating the need for a separate
db.getLastError(). Most write methods now return the status of the write operation, including error information. In previous versions, clients typically used the
db.getLastError()in combination with a write operation to verify that the write succeeded.
db.getLastError()can accept the following parameters:ParameterTypeDescription
wint or stringOptional. The write concern's
wtimeoutintOptional. The time limit in milliseconds.
error string provides error information on the
previous write operation.
db.getLastError() method itself encounters an error, such as an
incorrect write concern value, the
db.getLastError() throws an exception.
The following example issues a
that verifies that the preceding write operation, issued over the same
connection, has propagated to at least two members of the replica set.
getLastError and Write Concern for
all options, Write Concern for a conceptual
overview, MongoDB CRUD Operations for information about all
write operations in MongoDB.