Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade to mongo@3 #24

Closed
mcollina opened this issue Jan 12, 2018 · 5 comments
Closed

upgrade to mongo@3 #24

mcollina opened this issue Jan 12, 2018 · 5 comments
Labels
help wanted Help the community by contributing to this issue

Comments

@mcollina
Copy link
Member

mongo@3 has been a breaking release.

Can someone figure it out and update this?

@mcollina mcollina added the help wanted Help the community by contributing to this issue label Jan 12, 2018
@mcollina
Copy link
Member Author

cc @allevo ?

@allevo
Copy link
Member

allevo commented Jan 12, 2018

The changes are summarized here.

I'm 👍 particularly because the new version 3.0 support the mongo db server 3.6 too (released 1 month ago more or less).

For the CRUD operations, nothing changes.

The main breaking is during the connection.

From the link above:

MongoClient.connect('mongodb://localhost:27017/test', (err, db) => {
  // Database returned
});

become

MongoClient.connect('mongodb://localhost:27017/test', (err, client) => {
  // Client returned
  var db = client.db('test');
});

@allevo
Copy link
Member

allevo commented Jan 13, 2018

#25

@fox1t
Copy link
Member

fox1t commented Mar 10, 2018

Isn't this feature landed?

@allevo
Copy link
Member

allevo commented Mar 10, 2018

Hi @fox1t !
This feature is merged #25 and is landed with 0.5.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Help the community by contributing to this issue
Projects
None yet
Development

No branches or pull requests

3 participants