[SERVER-31629] Support creating a Status with a unique numeric code Created: 18/Oct/17 Updated: 30/Oct/23 Resolved: 02/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2017-10-23, Repl 2017-11-13 |
| Participants: |
| Description |
|
We currently ban creating a unique numeric code in a Status (rather than a uassert) because our unique code checker won't see them which will cause duplicate codes. This ticket is about making that work so we don't need to keep using ErrorCodes::BadValue everywhere. |
| Comments |
| Comment by Githook User [ 02/Nov/17 ] |
|
Author: {'name': 'Mathias Stearn', 'username': 'RedBeard0531', 'email': 'mathias@10gen.com'}Message: |
| Comment by Githook User [ 02/Nov/17 ] |
|
Author: {'name': 'Mathias Stearn', 'username': 'RedBeard0531', 'email': 'mathias@10gen.com'}Message: No reason to have two ways to express the same thing, and we can't get rid of |