[SERVER-18296] Cleanup DBClientCursor error handling Created: 01/May/15 Updated: 10/May/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Internal Client, Networking, Querying |
| Affects Version/s: | 3.1.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Alabi | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | move-sa, platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
In DBClientBase::query, if DBClientCursor can't be initialized, we return NULL. We should throw (perhaps, a UserException) instead. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Adam Midvidy [ 11/May/15 ] |
|
Marking this as "planned but not scheduled" as it isn't quite worth doing on its own and we will get to this when we (eventually...) do a larger cleanup of the DBClient hierarchy. |