Cartographie de mappage SQL vers Mongo
The whole part of persistent connections is outdated. In version 1.3.0:
«Removed the "persist" option, as all connections are now persistent. It can still be used, but it doesn't affect anything.»
As a matter of fact, this note is also wrong. Using option "persist" will throw an
Uncaught exception 'MongoConnectionException' with message '- Found unknown connection string option 'persist' with value 'x'
Connection
Sommaire
- Authentification
- Paires de réplication
- Fragmentation
- Support des sockets de domaine
- File d'attente de connexion (version 1.2.0-1.2.12 *seulement*)
- Les connexions persistantes (version supérieure à 1.1.4 *uniquement*)
La connexion à MongoDB est aussi simple que cela : new MongoClient, mais il existe aussi plusieurs options et plusieurs configurations. La page sur la méthode MongoClient::__construct() couvre toutes les options offertes par l'API, mais aussi, propose plusieurs cas pratiques.
add a note
User Contributed Notes
Connection - [3 notes]
Anonymous ¶
5 months ago
james at dunmore dot me dot uk ¶
10 months ago
We've got a strange gotcha (it maybe a bug with the mongo driver and we will raise an appropriate bug with them), but I think this is worth noting here.....
We were connecting to a replica set, but always getting "couldn't determine master" being returned. Connecting to individual notes without replicaset being set worked fine (directly to the master, or slave okay for reads). Replicaset working fine, and all setup okay.
The issue was our network setup, despite being able to resolve dbname-X.domain.com the server names were returning as dbname-X without the domain.
Pinging dbname-X worked, but for some reason the driver isn't resolving it. Adding the entry to hosts fixed this though.
daveg at smartbombinteractive dot com ¶
4 months ago
I was getting "couldn't determine master" when trying to connect to a replica set. It turns out there was a typo in my /etc/hosts entry for on of the replica set members.