[SERVER-12014] Getting a command's help message resets the last error stored for that connection Created: 09/Dec/13 Updated: 10/Dec/14 Resolved: 09/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Any time you run a command with the field help:1 included, it returns a help message for that command. Doing so will also reset the last error stored on that connection, which means that if you do a write, then run a command's "help" form, then call getLastError, you don't get the error from the write, you get a default write concern response. Given that running "help" on any command is guaranteed to be a read-only operation, we should not reset the last error when it is run. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 09/Dec/13 ] |
|
I think its correct, and also the GLE command is going to be deprecated in 2.6 |
| Comment by Andy Schwerin [ 09/Dec/13 ] |
|
I think it's still a command, so should reset last error. It's consistent behavior. |