(mongodb >=1.0.0)
MongoDB\Driver\Server::executeBulkWrite — Execute one or more write operations on this server
$namespace, MongoDB\Driver\BulkWrite $bulk, array|MongoDB\Driver\WriteConcern|null $options = null): MongoDB\Driver\WriteResultExecutes one or more write operations on this server.
A MongoDB\Driver\BulkWrite can be constructed with one or more write operations of varying types (e.g. updates, deletes, and inserts). The driver will attempt to send operations of the same type to the server in as few requests as possible to optimize round trips.
The default value for the "writeConcern" option will be
inferred from an active transaction (indicated by the
"session" option), followed by the
connection URI.
namespace (string)
A fully qualified namespace (e.g. "databaseName.collectionName").
bulk (MongoDB\Driver\BulkWrite)The write(s) to execute.
options
| Option | Type | Description |
|---|---|---|
| session | MongoDB\Driver\Session |
Eine Session, die mit dem Vorgang verknüpft werden soll. |
| writeConcern | MongoDB\Driver\WriteConcern |
Ein Schreibanliegen (Write Concern), das auf den Vorgang angewendet werden soll. |
Gibt bei Erfolg ein MongoDB\Driver\WriteResult zurück.
bulk does not contain any write operations.bulk has already been executed. MongoDB\Driver\BulkWrite objects may not be executed multiple times."session" in Kombination mit einer unbestätigten Schreibanweisung verwendet wird.
| Version | Beschreibung |
|---|---|
| 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.
|
| PECL mongodb 1.4.0 |
The third parameter is now an options array.
For backwards compatibility, this paramater will still accept a
MongoDB\Driver\WriteConcern object.
|
| PECL mongodb 1.3.0 |
MongoDB\Driver\Exception\InvalidArgumentException
is now thrown if bulk does not contain any write
operations. Previously, a
MongoDB\Driver\Exception\BulkWriteException was
thrown.
|
Hinweis: Es liegt in der Verantwortung des aufrufenden Codes, sicherzustellen, dass der Server in der Lage ist, den Schreibvorgang auszuführen. So schlägt beispielsweise die Ausführung eines Schreibvorgangs auf einem sekundären Server (mit Ausnahme seiner "lokalen" Datenbank) fehl.