Node js + Mongo db design

Question

I'm developing a node.js + mongoose webapp, and I have one doubt about database creation. This is how database is defined:

var user = new Schema({
 id : ObjectId,
 name : String,
 password : String,
 email : String,
 created : Date
});
var comment = new Schema({
 id : ObjectId,
 userId: ObjectId,
 content : String,
 created : Date
})

I want to link each comment with its user... So... which is the best way to do this? I thought to add one of these two to the comment Schema... but I don't know if its the correct answer or if there's another better:

userId: ObjectId,

or:

userObject: user

Thanks!

Hope you can help me!

Pierre · Accepted Answer · 2012-05-24 20:52:06Z

1

Well, it depends. There is no definitive answer to your question. Generally, I'd advise you not to use native MongoDB field references, which come with a slight size overhead.

For all of my projects, I would definitely choose the first solution, which is generally much more flexible and which will save you some disk space. At the cose of having to do one more request by yourself.

answered May 24, 2012 at 20:52

Pierre

6,1725 gold badges34 silver badges54 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Javier Manzano Over a year ago

So when I want to find all the comments from one user... It must be done as... db.Comment.find({userId: ObjectId("whatever")}) ??

Pierre Over a year ago

Yeah. Definitely what I'd do. db.Comment.find().where('userId', 'whatever') is more eye-sugar, through. If this is a function you often use, I'd strongly advise you to make this a Model method so you can call, for example, db.User.findComments(...), or db.Comments.findByUser(...).

Michelle Tilley Over a year ago

Mongoose also supports populate, which can do the extra query for you.

Pedro Galván Kondo · Accepted Answer · 2012-05-29 03:43:06Z

0

The simple data structure for this case is using what mongoose calls embedded documents.

As Brandon Tilley mentioned, you might also want to take a look at DBRef-like behavior and populate functionality of mongoose . This would allow you to handle your Comments entity as a separate, independent entity. The downside is that if you have a comment's instance and want to access the user's attributes, you have to populate your reference to the user first.

In the end, it depends on your use case and how you'd rather navigate your info. I say don't think too much about it and try any. If you decide later that another structure works best, just change it. Fortunately, this is very simple with MongoDB and NoSQL in general.

edited May 29, 2012 at 3:43

answered May 29, 2012 at 3:35

Pedro Galván Kondo

34 bronze badges

Collectives™ on Stack Overflow

Node js + Mongo db design

2 Answers 2

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related