MongoDB\Driver\Server::executeCommand — Execute a database command on this server
$options= array()): MongoDB\Driver\Cursor
Executes the command on this server.
This method applies no special logic to the command. Although this method
"writeConcern" options, which will be incorporated into
the command document, those options will not default to corresponding values
from the MongoDB
Connection URI nor will the MongoDB server version be taken into
account. Users are therefore encouraged to use specific read and/or write
command methods if possible.
"readPreference"option does not control the server to which the driver issues the operation; it will always be executed on this server object. Instead, it may be used when issuing the operation to a secondary (from a replica set connection, not standalone) or mongos node to ensure that the driver sets the wire protocol accordingly or adds the read preference to the operation, respectively.
A read concern to apply to the operation.
This option is available in MongoDB 3.2+ and will result in an exception at execution time if specified for an older server version.
A read preference to use for selecting a server for the operation.
A session to associate with the operation.
A write concern to apply to the operation.
If you are using a
"session" which has a transaction
in progress, you cannot specify a
"writeConcern" option. This will result in an
being thrown. Instead, you should set these two options when you create
the transaction with
成功した場合に MongoDB\Driver\Cursor を返します。
"session"option is used with an associated transaction in combination with a
"session"option is used in combination with an unacknowledged write concern.
|PECL mongodb 1.4.4||
will be thrown if the
|PECL mongodb 1.4.0||
The third parameter is now an
注意: It is the caller's responsibility to ensure that the server is capable of executing the write operation. For example, executing a write operation on a secondary (excluding its "local" database) will fail.