MongoDB\Driver\WriteConcern::__construct — Construct immutable WriteConcern
Creates a new WriteConcern.
|1||Requests acknowledgement that the write operation has propagated to the standalone mongod or the primary in a replica set. This is the default write concern for MongoDB.|
|0||Requests no acknowledgment of the write operation. However, this may return information about socket exceptions and networking errors to the application.|
|<integer greater than 1>||Numbers greater than 1 are valid only for replica sets to request acknowledgement from specified number of members, including the primary.|
Requests acknowledgment that write operations have propagated to the majority of voting nodes, including the primary, and have been written to the on-disk journal for these nodes.
Prior to MongoDB 3.0, this refers to the majority of replica set members (not just voting nodes).
|string||A string value is interpereted as a tag set. Requests acknowledgement that the write operations have propagated to a replica set member with the specified tag.|
How long to wait (in milliseconds) for secondaries before failing.
wtimeout causes write operations to return with an error (WriteConcernError) after the specified limit, even if the required write concern will eventually succeed. When these write operations return, MongoDB does not undo successful data modifications performed before the write concern exceeded the wtimeout time limit.
|0||Block indefinitely. This is the default.|
|<integer greater than 0>||Milliseconds to wait until returning.|
Wait until mongod has applied the write to the journal.
Example #1 MongoDB\Driver\WriteConcern::__construct() example
/* Request write acknowledgement from the majority of the replica set nodes */
$wc = new MongoDB\Driver\WriteConcern(MongoDB\Driver\WriteConcern::MAJORITY, 500);
/* Request write acknowledgement from a node configured with the "MultipleDC" tag */
$wc = new MongoDB\Driver\WriteConcern("MultipleDC", 500);