For PHPLIB-228, 4c61d3c added an earlier server selection in MongoDB\Collection::findOne() but neglected to remove the original server selection before the operation is executed. As such, it's possible for the driver to select a secondary that supports read concerns, inject a default read concern, and then execute the operation on an older secondary that does not support read concerns, thereby triggering an error (as described here).
- is related to
-
PHPLIB-228 ReadConcern default should only be set when supported by the server
- Closed
- links to