While working on a MERN stack project, I came across a situation where I wanted to populate a field but also populate a field inside that populated...
For further actions, you may consider blocking this person and/or reporting abuse
From the outside, this seems like basically creating
JOINfunctionality from an RDBMS. That's not a bad thing! It turns out that sometimes an RDBMS needs document-style records, and sometimes document DBs need relations :) Just wanted to make the comparison in case it helps anyone else (and to make sure I understand it correctly).Correct !!...And Nice comparision. :)
Mongo newbie here ππ»
Is it possible to do findOne after the populate?
The query string I have available belongs to the referenced document. I would like to first populate it and then find the document I am looking for.
Other wise I first need to do a findOne in one collection and pass the result to another collectionβs findOne.
I am trying to avoid an unnecessary findOne operation but maybe I am overthinking it and its okay to do multiple findOneβs to reach a result?
Another solution comes to my mind is to make the query string I have available an indexed unique field so I can directly do findOne.
Great point you made there. I never tried that, but I guess you can give it try. For cases like these, I tend to use aggregation.
Merci!!! m'a beaucoup aidΓ© cette information!! :)
Je vous en price. π
I have a schema named Product inside I have added another schema named Category. I want to get all the products related to a particular category(_id) passed. how do I do that. please help.
I think you can simply use
findproducts and check forcategoryusing$inoperator. If it doesn't help then can you show a dummy schema and what you want in result?Thank you for great article.
But I have a concern, what if I use my custom Id:string as a key, what will the type be rather than mongoose.Schema.Types.ObjectId?
There is a concept called "Virtuals". I came across it when I was thinking the same thing. I can only give you hint about it because I have not learned or applied them. In virtuals, you define the conditions for virtuals: 'localField' and 'foreignField'. Local field refers to the name of the field of your current Schema. Foreign field is the name of the field which you are using in other schema to refer to your current Schema. Then you use populate normally.
There maybe some mistake in above example but hope it helps you understand the basics atleast.
Maybe once I get time to study, I will write about it as well. :)
Thanks, that's helpful. But the "yahoo" could be anything, when we call
.populate("field name of Authors"). There are something still not clear. However, I get over it by modify data type of _id field.Good...things are not 100% clear to me as well...but I am sure after trying and testing we can understand it better :)
Hello paras wanted to know how you can find or filter items based on the populated items
Hi Neural. I don't think, we can find or filter items based on populated items. It may also slow down the query as well.
I would say, go for aggregation, because in aggregation we have better control over how we structure and filter data in different steps. Populate is good for simple to intermediate scenarios but aggregation is more helpful when you need to handle a little complex to advance scenarios
Hi Paras,
This was a nice read. I am going to implement this for my MEAN project. A Couple of questions.
I have a Log collection, which has 4 ObjectId type fields. i.e. client, service, executive, manager - of course apart from its own fields. And when on frontend, the Log is displayed, I am planning to populate all these 4 (i.e. Client Name, Category, Sub Category, Rating), (Service Name, Service Freq), ExecName and ManagerName.
The Log display on frontend has Search and filter options on various fields. So when a user searches or applies filters the backend Mongoose query will run again.
What would be the performance impact if the number of entries in Log collection is in the range to 5000 - 50,000?
For the above type of case would there be any other option for fetching the related data OR this is the best option.
Though populate is not bad. It is optimised. But there is a another way. If you know about aggregation framework in mongodb then there is a
$lookupoption that you can add in pipeline. I am still learning about aggregation framework. I have read that $lookup is faster than populate. Try to find more about itJust know one thing. That populate makes a second call to database. So in your case 4 populates = 4 calls.
Or, you can do a live test :p...run query with populate and check its performance then run query with $lookup pipeline and compare its performance. (mongodb has ways to check query performance)
I hope it helps you. All the best for your project :)
Thanks Paras for your quick response. It surely helps.
You are welcome sir !!
$lookup cannot be sharded and so it limits your scaling, super annoying constraint because I loved this stage until I spotted that.
Okayy. thank you !! I didn't know that :)
I still have to learn more about sharding. Never tried it.
Thank you for great article.
Welcome β€οΈ
does the populate use find() query behind the scenes and if it does, will it also activate all the pre query middlewares of the model whose documents are used to populate?
Suppose .populate('comments')
will it also run the pre query middlewares of the ref of comments?
Yes we can say it makes a call to find method behind the scenes. But I don't know about pre query middlewares. You have to try it once to see the outcome. Maybe it will pre query middlewares. Never really tried :)
I have another question, that we also have the option to select certain fields while using populate like
.populate({path: 'comments', select: 'content name'}). Do you have some idea that it only summons that selected field or summons the whole documents and then selects the field?
Honestly I don't have idea about this one. But I can say that returning whole docs is easier because it doesn't have to convert it to partial one and return BSON data directly. So selecting specific fields adds an overhead. Don't let it discourage you from using select in populate or find.
Awesome . I knew this In django , Finally Got one for Node π€
does populate in mongoose issue a separate DB call for fetching the referenced documents or does it translate to a $lookup and issue a single query?
No, it doesn't translate to a $lookup and Yes, it makes another query to db to get the required data.
Good question !
I see. yeah clientside joins are a difficult problem to solve. I've been trying to do that with my c# mongodb library but still haven't found a proper/ user friendly way. was expecting to steal it from mongoose if they've managed it π
hahaha...i think you have to use $lookup and $aggregation :p
Great bro
Very much helpful
Thank you !!! :)
i don't know why populate is not working for me i get a empty array
don't forget to add ids in that array
yes that's why i was getting an empty array, thank you
:) good luck !
This is so much simple and concise. Thanks, Paras.
Thank you !!...Glad you found it useful. :)
Absolute delight to read.
thanks !!
good one,nice
thanks :)
Cool tip didnβt know this one.
Glad you found it useful :)
Glad you found t, It's very helpfull
Thank you !! :)
I wonder why the populate method totally refused to work in my Express.js project. Tried everything as stated in the Mongoose Populate() documentation, yet nothing works.
really ?!.. what error are you getting ?
Thankyou. It helped.
Welcome !! :)