[GODRIVER-256] Ensure Cursor implementations return Close error on Close Created: 21/Feb/18 Updated: 19/Apr/18 Resolved: 05/Apr/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | 0.0.1 |
| Fix Version/s: | 0.0.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kristofer Brandow (Inactive) | Assignee: | Kristofer Brandow (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | Stitch | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | GODRIVER Alpha UX | ||||
| Description |
|
According to the interface documentation for ops.Cursor: "Returns the error status of this cursor so that clients do not have to call Err() separately". This would result in confusion around where an error actually originated and what error to return when both a Cursor error and a Close error occur. When the Cursor implementations are updated for the command structure, ensure that the Close method only returns errors related to closing the Cursor. |
| Comments |
| Comment by Kristofer Brandow (Inactive) [ 05/Apr/18 ] |
|
This was handled as part of |