(mongodb >=1.4.0)
MongoDB\Driver\Manager::executeReadWriteCommand — Execute a database command that reads and writes
$db, MongoDB\Driver\Command $command, ?array $options = null): MongoDB\Driver\CursorExecutes the command on the primary server.
This method will apply logic that is specific to commands that read and write
(e.g. » aggregate).
Default values for the "readConcern" and
"writeConcern" options will be inferred from an active
transaction (indicated by the "session" option), followed
by the connection URI.
db (string)command (MongoDB\Driver\Command)options
| Option | Type | Description |
|---|---|---|
| readConcern | MongoDB\Driver\ReadConcern | 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. |
| session | MongoDB\Driver\Session | A session to associate with the operation. |
| writeConcern | MongoDB\Driver\WriteConcern | A write concern to apply to the operation. |
If you are using a "session" which has a transaction
in progress, you cannot specify a "readConcern" or
"writeConcern" option. This will result in an
MongoDB\Driver\Exception\InvalidArgumentException
being thrown. Instead, you should set these two options when you create
the transaction with
MongoDB\Driver\Session::startTransaction().
Returns MongoDB\Driver\Cursor on success.
"session" option is used with an associated transaction in combination with a "readConcern" or "writeConcern" option."session" option is used in combination with an unacknowledged write concern.| Versione | Descrizione |
|---|---|
| PECL mongodb 1.4.4 |
MongoDB\Driver\Exception\InvalidArgumentException
will be thrown if the "session" option is used in
combination with an unacknowledged write concern.
|