Skip to content
This repository has been archived by the owner on Nov 11, 2020. It is now read-only.

Fix handling of client options (e.g. socket timeout) in command helpers #196

Merged
merged 2 commits into from
Dec 9, 2014

Conversation

jmikola
Copy link
Member

@jmikola jmikola commented Dec 9, 2014

This fixes code originally introduced in a3aaffa. For convenience, command helpers take a single options array. Previously, all of those options were merged into the command document, which meant that client options were never seen by the driver. Now, client options are split from the helper's single options array so they may be passed to MongoDB::command() appropriately.

This fixes code originally introduced in a3aaffa. For convenience, command helpers take a single options array. Previously, all of those options were merged into the command document, which meant that client options were never seen by the driver. Now, client options are split from the helper's single options array so they may be passed to MongoDB::command() appropriately.
@jmikola jmikola added the bug label Dec 9, 2014
@jmikola jmikola added this to the 1.1.7 milestone Dec 9, 2014
@jmikola jmikola merged commit ba9c8bc into 1.1.x Dec 9, 2014
jmikola added a commit that referenced this pull request Dec 9, 2014
@jmikola jmikola deleted the 1.1-command-client-options branch December 9, 2014 22:48
jmikola added a commit that referenced this pull request Dec 10, 2014
This was originally added in #196 when fixing handling of command and client options for Collection command wrappers; however, #198 moved conversion of "timeout" to Database::command(), so we no longer need to do it in each Collection command wrapper.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant