-
Type: Bug
-
Resolution: Done
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Docs for Manager::executeCommand() incorrectly state that the URI's read preference may be used:
Selects a server according to the "readPreference" option and executes the command on that server. By default, the read preference from the MongoDB Connection URI will be used.
This appears to be copypasta from executeReadCommand dating back to php/doc-en@77ff972 for PHPC-834.
Moreover, the various execute methods for both Manager and Server don't discuss that options may be inherited from an active transaction. This is mentioned in the corresponding libmongoc docs:
- mongoc_client_command_with_opts
- mongoc_client_read_command_with_opts
- mongoc_client_read_write_command_with_opts
- mongoc_client_write_command_with_opts
The rules for inheriting from a transaction may be more subtle for executeQuery and executeBulkWrite:
- is related to
-
PHPC-834 Add Read, ReadWrite, and Write command execute methods
- Closed
- related to
-
CDRIVER-5578 mongoc_client_read_command_with_opts docs omit client as a source for the read concern option
- Backlog