-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 1.11.6
-
Component/s: Command & Dispatch
-
None
-
Not Needed
-
Example code:
_, err := client.Database("mydb").RunCommandCursor(nil, bson.D{ {"explain", bson.D{{"find", "mycollection"}}}, {"verbosity", "executionStats"}, })
This simpler example fails in the same way:
_, err := client.Database("mydb").RunCommandCursor(nil, bson.D{ {"ping", 1}, })
Error:
cursor should be an embedded document but is of BSON type invalid
It's quite possible that i'm just doing something wrong. In which, case the bug is just that the error message does not indicate what I did wrong. However, im pretty sure there's a real bug here preventing this from working.
I see that `RunCommandCursor` calls `ResultCursor`, which calls `NewCursorResponse` with `c.result`. `c.result` only appears to ever be set by `Execute` which, is never called. `NewCursorResponse` then returns the above error when it tries to verify the type of the "cursor" field on a nil document.
- clones
-
GODRIVER-1114 RunCommandCursor always fails and returns an error message referencing internal driver details
- Closed
- is duplicated by
-
GODRIVER-1134 Database.RunCommandCursor is not work
- Closed