Exporting Mongoose model without waiting for connection 'open' event
up vote
0
down vote
favorite
I am exporting a Mongoose model and able to use it in other files, but I am confused why it is working. Why do I not need to wait for the connection open event to fire? The Mongoose getting started tutorial talks about needing to wait to work with the connection until this event fires. I was about to refactor so that I exported a Promise that would resolve upon firing of the 'open' event, but refrained from complicating things since the below works.
This answer suggests that it is not necessary to wait for the 'open' event.
var mongoose = require('mongoose');
mongoose.connect('mongodb://localhost/XXX');
var db = mongoose.connection;
var listingSchema = new mongoose.Schema({
id: Number,
})
var Listing = mongoose.model('Listing', listingSchema);
module.exports = Listing;
node.js mongodb mongoose
asked Nov 12 at 0:06
mrwnt10
186214
add a comment |
up vote
0
down vote
favorite
I am exporting a Mongoose model and able to use it in other files, but I am confused why it is working. Why do I not need to wait for the connection open event to fire? The Mongoose getting started tutorial talks about needing to wait to work with the connection until this event fires. I was about to refactor so that I exported a Promise that would resolve upon firing of the 'open' event, but refrained from complicating things since the below works.
This answer suggests that it is not necessary to wait for the 'open' event.
var mongoose = require('mongoose');
mongoose.connect('mongodb://localhost/XXX');
var db = mongoose.connection;
var listingSchema = new mongoose.Schema({
id: Number,
})
var Listing = mongoose.model('Listing', listingSchema);
module.exports = Listing;
node.js mongodb mongoose
asked Nov 12 at 0:06
mrwnt10
186214
This is a "rare" case where it is absolutely true that the age of the answer there ( from 2012 ) actually does matter. The problem is that the underlying MongoDB node driver used changed it's API in recent years. Previously "mongoose" used a method which would establish connections "later" as you used any API actions (save(),create()etc ). Whist that "sort of" happens now, the method to establish the connections the old way has been removed. So it's really best practice to "await" the initial connection. It always was "nest" really, but older API "hid it away". Now it does not.
– Neil Lunn
Nov 12 at 0:25
Also BTW the "modern" approach would be toawaittheconnect()instead of listening for the'open'event anyway.
– Neil Lunn
Nov 12 at 0:26
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am exporting a Mongoose model and able to use it in other files, but I am confused why it is working. Why do I not need to wait for the connection open event to fire? The Mongoose getting started tutorial talks about needing to wait to work with the connection until this event fires. I was about to refactor so that I exported a Promise that would resolve upon firing of the 'open' event, but refrained from complicating things since the below works.
This answer suggests that it is not necessary to wait for the 'open' event.
var mongoose = require('mongoose');
mongoose.connect('mongodb://localhost/XXX');
var db = mongoose.connection;
var listingSchema = new mongoose.Schema({
id: Number,
})
var Listing = mongoose.model('Listing', listingSchema);
module.exports = Listing;
node.js mongodb mongoose
asked Nov 12 at 0:06
mrwnt10
186214
I am exporting a Mongoose model and able to use it in other files, but I am confused why it is working. Why do I not need to wait for the connection open event to fire? The Mongoose getting started tutorial talks about needing to wait to work with the connection until this event fires. I was about to refactor so that I exported a Promise that would resolve upon firing of the 'open' event, but refrained from complicating things since the below works.
This answer suggests that it is not necessary to wait for the 'open' event.
var mongoose = require('mongoose');
mongoose.connect('mongodb://localhost/XXX');
var db = mongoose.connection;
var listingSchema = new mongoose.Schema({
id: Number,
})
var Listing = mongoose.model('Listing', listingSchema);
module.exports = Listing;
node.js mongodb mongoose
node.js mongodb mongoose
asked Nov 12 at 0:06
mrwnt10
186214
asked Nov 12 at 0:06
mrwnt10
186214
asked Nov 12 at 0:06
mrwnt10
186214
asked Nov 12 at 0:06
mrwnt10
186214
asked Nov 12 at 0:06
mrwnt10
186214
186214
This is a "rare" case where it is absolutely true that the age of the answer there ( from 2012 ) actually does matter. The problem is that the underlying MongoDB node driver used changed it's API in recent years. Previously "mongoose" used a method which would establish connections "later" as you used any API actions (save(),create()etc ). Whist that "sort of" happens now, the method to establish the connections the old way has been removed. So it's really best practice to "await" the initial connection. It always was "nest" really, but older API "hid it away". Now it does not.
– Neil Lunn
Nov 12 at 0:25
Also BTW the "modern" approach would be toawaittheconnect()instead of listening for the'open'event anyway.
– Neil Lunn
Nov 12 at 0:26
add a comment |
This is a "rare" case where it is absolutely true that the age of the answer there ( from 2012 ) actually does matter. The problem is that the underlying MongoDB node driver used changed it's API in recent years. Previously "mongoose" used a method which would establish connections "later" as you used any API actions (save(),create()etc ). Whist that "sort of" happens now, the method to establish the connections the old way has been removed. So it's really best practice to "await" the initial connection. It always was "nest" really, but older API "hid it away". Now it does not.
– Neil Lunn
Nov 12 at 0:25
Also BTW the "modern" approach would be toawaittheconnect()instead of listening for the'open'event anyway.
– Neil Lunn
Nov 12 at 0:26
This is a "rare" case where it is absolutely true that the age of the answer there ( from 2012 ) actually does matter. The problem is that the underlying MongoDB node driver used changed it's API in recent years. Previously "mongoose" used a method which would establish connections "later" as you used any API actions (
save(), create() etc ). Whist that "sort of" happens now, the method to establish the connections the old way has been removed. So it's really best practice to "await" the initial connection. It always was "nest" really, but older API "hid it away". Now it does not.– Neil Lunn
Nov 12 at 0:25
This is a "rare" case where it is absolutely true that the age of the answer there ( from 2012 ) actually does matter. The problem is that the underlying MongoDB node driver used changed it's API in recent years. Previously "mongoose" used a method which would establish connections "later" as you used any API actions (
save(), create() etc ). Whist that "sort of" happens now, the method to establish the connections the old way has been removed. So it's really best practice to "await" the initial connection. It always was "nest" really, but older API "hid it away". Now it does not.– Neil Lunn
Nov 12 at 0:25
Also BTW the "modern" approach would be to
await the connect() instead of listening for the 'open' event anyway.– Neil Lunn
Nov 12 at 0:26
Also BTW the "modern" approach would be to
await the connect() instead of listening for the 'open' event anyway.– Neil Lunn
Nov 12 at 0:26
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254488%2fexporting-mongoose-model-without-waiting-for-connection-open-event%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This is a "rare" case where it is absolutely true that the age of the answer there ( from 2012 ) actually does matter. The problem is that the underlying MongoDB node driver used changed it's API in recent years. Previously "mongoose" used a method which would establish connections "later" as you used any API actions (
save(),create()etc ). Whist that "sort of" happens now, the method to establish the connections the old way has been removed. So it's really best practice to "await" the initial connection. It always was "nest" really, but older API "hid it away". Now it does not.– Neil Lunn
Nov 12 at 0:25
Also BTW the "modern" approach would be to
awaittheconnect()instead of listening for the'open'event anyway.– Neil Lunn
Nov 12 at 0:26