[SERVER-112] more parsable / easier to work with format for server error messages Created: 22/Jun/09 Updated: 12/Jul/16 Resolved: 28/Dec/09 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Michael Dirolf | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
the error messages we get now are a bit tricky to handle programmatically |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 28/Dec/09 ] |
|
to get next id: |
| Comment by auto [ 28/Dec/09 ] |
|
Author: {'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: use code in getLastError |
| Comment by auto [ 28/Dec/09 ] |
|
Author: {'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: Exception classess need codes too |
| Comment by auto [ 28/Dec/09 ] |
|
Author: {'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: uassert/massert take error code |