Summary

The CRUD specification is unclear about the correct method of handling write concern errors for single-statement writes (i.e. insertOne, updateOne, updateMany, replaceOne, deleteOne, and deleteMany.

Its is possible that driver implement these differently and behavior is inconsistent.

Motivation

Who is the affected end user?

Anyone using the CRUD API

How does this affect the end user?

Confusing behavior - potentially misreporting of WriteConcernErrors

How likely is it that this problem or use case will occur?

Edge case - see linked HELP ticket

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance

Is this issue urgent?

Not urgent

Is this ticket required by a downstream team?

N/A

Is this ticket only for tests?

Extra tests should be added as well as a clarification in the language/

Acceptance Criteria

All write concern errors are correctly reported back to the user.