You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the new features of the v3.0 (congrats for the release ! 👍), I noticed mongoose is using the latest mongodb driver.
I see that the driver now offers a possibility to use a specific Mongos connection, but I couldn't find any mongoose issue or documentation talking about it. Is it planned for a future release ?
The text was updated successfully, but these errors were encountered:
You've always been able to connect to Mongos with the driver or Mongoose. I'll have to look into why we have a separate class now. Does it not work anymore?
Looking at the new features of the v3.0 (congrats for the release ! ), I noticed mongoose is using the latest mongodb driver.
I see that the driver now offers a possibility to use a specific Mongos connection, but I couldn't find any mongoose issue or documentation talking about it. Is it planned for a future release ?
�
Reply to this email directly or view it on GitHub.
There is no particular problem with the current implementation, the separate class just seem to take advantage of the fact it's dealing with a mongos, notably for read preferences and reconnection mechanism.
There is no particular problem with the current implementation, the
separate class just seem to take advantage of the fact it's dealing with a
mongos, notably for read preferences and reconnection mechanism.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1037#issuecomment-7586090.
Hello,
Looking at the new features of the v3.0 (congrats for the release ! 👍), I noticed mongoose is using the latest mongodb driver.
I see that the driver now offers a possibility to use a specific Mongos connection, but I couldn't find any mongoose issue or documentation talking about it. Is it planned for a future release ?
The text was updated successfully, but these errors were encountered: