[CXX-1749] mongocxx api doc: read_concern can also be set in transaction options Created: 26/Mar/19 Updated: 07/Feb/24 |
|
| Status: | Backlog |
| Project: | C++ Driver |
| Component/s: | Documentation |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Henrik Ingo (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Epic Link: | Reference Docs Improvements | ||||||||
| Description |
|
http://mongocxx.org/api/mongocxx-3.4.0/classmongocxx_1_1read__concern.html says: "Read concern can be set at the client, database, or collection level." This should be updated to say that it can also be set in mongocxx::options::transaction. Also, it is worth mentioning that this is the only (non-deprecated) way to set read_concern for a transaction. (See also DRIVERS-619) |