[CXX-1085] Inconsistent API for operation level write concern Created: 12/Oct/16 Updated: 03/Jun/20 Resolved: 26/Jun/17 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | API |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.0-rc0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | Patrick Freed |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Some operations, like Insert_one, allow write_concern in an options object. Others, like find_one_and_delete, do not and only take the value from the collection level default. This may have been due to mongoc limitations, but with the addition of the xxx_xxx_with_opts functions, we have more API choices now. For consistency, we should add write_concern to all write operation options classes. |
| Comments |
| Comment by Githook User [ 26/Jun/17 ] |
|
Author: {u'username': u'patrickfreed', u'name': u'Patrick Freed', u'email': u'fridpatrick@gmail.com'}Message: |