-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: API
-
None
Unlike write_concern and read_preference, I cannot set read_concern for individual operations like mongocxx::options::find, mongocxx::options::update & co. It would make sense for read_concern to be supported in all the same contexts as write_concern + matching read operations.
- related to
-
CXX-1749 mongocxx api doc: read_concern can also be set in transaction options
- Backlog