Docs Menu

db.getLastError()

On this page

  • Definition
  • Behavior
  • Example
db.getLastError(<w>, <wtimeout>)

Starting in MongoDB 5.0, db.getLastError() is deprecated. For more information and alternatives, see Deprecated Wire Protocol Opcodes.

Specifies the level of write concern for confirming the success of previous write operation issued over the same connection and returns the error string for that operation.

When using 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.

The db.getLastError() can accept the following parameters:

Parameter
Type
Description
w
int or string
Optional. The write concern's w value.
wtimeout
int
Optional. The time limit in milliseconds.

The returned error string provides error information on the previous write operation.

If the 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 db.getLastError() operation that verifies that the preceding write operation, issued over the same connection, has propagated to at least two members of the replica set.

db.getLastError(2)
Tip
See also:

getLastError and Write Concern for all options, Write Concern for a conceptual overview, MongoDB CRUD Operations for information about all write operations in MongoDB.

←  db.getCollectionNames()db.getLastErrorObj() →
Give Feedback
© 2022 MongoDB, Inc.

About

  • Careers
  • Investor Relations
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2022 MongoDB, Inc.