Re mocking implications of final nature of MongoDB\Driver\Manager :
Final classes can be mocked through an indirection using a wrapper class.
(mongodb >=1.0.0)
The MongoDB\Driver\Manager is the main entry point to the extension. It is responsible for maintaining connections to MongoDB (be it standalone server, replica set, or sharded cluster).
No connection to MongoDB is made upon instantiating the Manager. This means the MongoDB\Driver\Manager can always be constructed, even though one or more MongoDB servers are down.
Any write or query can throw connection exceptions as connections are created lazily. A MongoDB server may also become unavailable during the life time of the script. It is therefore important that all actions on the Manager to be wrapped in try/catch statements.
$uri
= "mongodb://127.0.0.1/"
, array $uriOptions
= array()
, array $driverOptions
= array()
)$namespace
, MongoDB\Driver\BulkWrite $bulk
, array $options
= array()
) : MongoDB\Driver\WriteResult$db
, MongoDB\Driver\Command $command
, array $options
= array()
) : MongoDB\Driver\Cursor$namespace
, MongoDB\Driver\Query $query
, array $options
= array()
) : MongoDB\Driver\Cursor$db
, MongoDB\Driver\Command $command
, array $options
= array()
) : MongoDB\Driver\Cursor$db
, MongoDB\Driver\Command $command
, array $options
= array()
) : MongoDB\Driver\Cursor$db
, MongoDB\Driver\Command $command
, array $options
= array()
) : MongoDB\Driver\CursorExample #1 MongoDB\Driver\Manager::__construct() basic example
var_dump()ing a MongoDB\Driver\Manager will print out various details about the manager that are otherwise not normally exposed. This can be useful to debug how the driver views your MongoDB setup, and which options are used.
<?php
$manager = new MongoDB\Driver\Manager("mongodb://localhost:27017");
var_dump($manager);
?>
以上例程的输出类似于:
object(MongoDB\Driver\Manager)#1 (3) { ["request_id"]=> int(1714636915) ["uri"]=> string(25) "mongodb://localhost:27017" ["cluster"]=> array(13) { ["mode"]=> string(6) "direct" ["state"]=> string(4) "born" ["request_id"]=> int(0) ["sockettimeoutms"]=> int(300000) ["last_reconnect"]=> int(0) ["uri"]=> string(25) "mongodb://localhost:27017" ["requires_auth"]=> int(0) ["nodes"]=> array(...) ["max_bson_size"]=> int(16777216) ["max_msg_size"]=> int(50331648) ["sec_latency_ms"]=> int(15) ["peers"]=> array(0) { } ["replSet"]=> NULL } }
Re mocking implications of final nature of MongoDB\Driver\Manager :
Final classes can be mocked through an indirection using a wrapper class.
According to Mongo, this (i.e., MongoDB\Driver\Manager) is an "entry point" for the extension:
"This class serves as an entry point for the MongoDB PHP Library. It is the preferred class for connecting to a MongoDB server or cluster of servers and acts as a gateway for accessing individual databases and collections. MongoDB\Client is analogous to the driver's MongoDB\Driver\Manager class, which it composes."
copied from here: https://docs.mongodb.com/php-library/master/reference/class/MongoDBClient/
However, any comparison of the "mongodb" docs here on php.net versus the "mongodb driver" docs on mongo's site shows dramatic and ever-changing differences.
It's worth noting that Manager is final, so you cannot mock it easily with tools like PhpUnit.