Okay so having 30 000 documents limit, what can we do if we have 100 000 users? One way I can think of is to separate separate them in different collections by first letter of the name e.g. A-H, I-N, O-Z. But is it good and sustainable solution?
20:46 Is there a way to create an index on a collection via code (rather than in Compass)? Just a pointer to documentation would be great, if it exists.
25:03 Is it possible to set the default collation strength on a collection AFTER the collection has been created? I can imagine many real-world use cases where MongoDB users recognize that they can benefit from a case-insensitive index, but their collections already exist. Just a pointer to documentation would be great, if it exists.
Thanks first for this informative video and I have one question about restructuring the data(inspirationWomen) into two collections to optimize the website this is the optimal solution ?? or we can keep the old collection as it and for the home page on the website just selecting first_name, last_name have the same performance target??
There was no need to replicate the name and last name, whatever consumer of this data could simply pull the document from the first collection (that contains the name and the last name) and then pull the details, no need to replicate.
there was need to do it to make collection less than 500mb wired tiger cash size so that new little collection with only first names and second names could fit in it
✅ Sign-up for a free cluster at: mdb.link/free-mHeP5IbozDU
✅ Get help on our Community Forums: mdb.link/community-mHeP5IbozDU
So easy to understand with examples you provided. Thnaks for the video!
You are doing a great job. Thanks a lot for such informative and concise videos.
Hi, is there any difference between collation strength 1 and 2? and what are strengths 3, 4, 5 represent? Thanks for the great video
MAN! THE PARKS AND REC REFERENCES ARE SUPER AWESOME!!! LOVED THE VIDEO!
This is extremely helpful. Thank you!
Okay so having 30 000 documents limit, what can we do if we have 100 000 users? One way I can think of is to separate separate them in different collections by first letter of the name e.g. A-H, I-N, O-Z. But is it good and sustainable solution?
thanks
20:46 Is there a way to create an index on a collection via code (rather than in Compass)? Just a pointer to documentation would be great, if it exists.
25:03 Is it possible to set the default collation strength on a collection AFTER the collection has been created? I can imagine many real-world use cases where MongoDB users recognize that they can benefit from a case-insensitive index, but their collections already exist. Just a pointer to documentation would be great, if it exists.
awesome video!
Very nice❤😂🎉
Thanks first for this informative video and I have one question about restructuring the data(inspirationWomen) into two collections to optimize the website this is the optimal solution ?? or we can keep the old collection as it and for the home page on the website just selecting first_name, last_name have the same performance target??
Same question on my mind... if projection would so same thing
Awesome video ++++++++++++++++++++ 😃
Invaluable!
Reggea--ex
There was no need to replicate the name and last name, whatever consumer of this data could simply pull the document from the first collection (that contains the name and the last name) and then pull the details, no need to replicate.
there was need to do it to make collection less than 500mb wired tiger cash size so that new little collection with only first names and second names could fit in it
Mam can you please create a small project using spring boot and mongodb which can help millions of people. You look so cute❤️.