ASP.NET Core Web API .NET 6 2022 - 3. Many-To-Many Relationships

[@spencersedano]

This is the first time that I understand why write or anything, I had no idea when I first saw it. Thanks a lot!

[@TeddySmithDev]

Cool name lol. Thanks for commenting!!!

[@raggardy]

Teddy, thanks so much for this series! Really simple explainations of 1-2-1 and many to many.Glad I stumbled across your channel and keep up the great work

[@Tanaka-Buchou]

Thank you, Teddy. Your explanations are precise.

[@vicman3122]

Dude you are great, Thanks I'm going to recomend your videos to my friends

[@trashbin2166]

Dude you're sooo good at explaining stuff (loved that pokemon analogy)! Keep it up!

[@segunbabalola7430]

You don't know how much what you said from 8:26 to 9:20 mean to a lot of people. The encouragement is great

[@JugalSingh]

Really needed to hear that

[@saladlord7613]

Yeah just what I needed

[@NamNguyen-oz8uj]

Thank you for your great videos, Teddy 🎉🎉🎉🎉🎉🎉

[@hoangphuc1072]

Thank you for your great videos, Teddy

[@reginaabdu931]

Thanks, Teddy! From your subscriber from Uzbekistan!

[@dq9342]

Thanks again, Teddy! Keep up the good teaching!

[@itsrino9851]

I love how you added some side productivity shortcuts, like the get definition !! Its little things like this that make a big difference in workflow! thanks for that!

[@trungnguyencong3216]

thank you so much your repo is a life saver I have hard time understand relationship many to many

[@chadgregory9037]

I like to think about these tables and relationships in terms of an object being created. So for example... a many to many relationship.... we HAVE to have that join table because that is literally everything and that's where the "magic" happens.... so for example, when a trainer catches a pokemon, the pokemon entity already existed, it already had its own unique ID... the trainer/owner entity already existed and it had its own unique ID... so when the trainer catches a new pokemon (creation of a new object) the entry is occurring on the join table..... and then say a view model would have a trainer entity having an Icollection and an sql JOIN would be done in order to pull the necessary data in to make it available to the application

[@TeddySmithDev]

This is really cool

[@chadgregory9037]

@@TeddySmithDev I hope it's right lol I let my brain get a little pretzel f-kd with the different kinds of models and use cases lol

[@RalphWeber-z2x]

Great Pokemon explanation of many to many

[@onurakmese2129]

Thank you bro, you're my hero

[@kvelez]

Great, I learned a lot about relationships and keys.

[@ЕгорБаранов-ь1э]

лучший учитель!

[@koenmjaar]

You might want to inform the people watching that adding the collections is not a must. For me it came over as this is a MUST thing to do, while it's not (correct me if I'm wrong lol). F.e. If I have a table Occupation linked to the table User, I don't want to fetch every User linked to one occupation at all times, that's why we would write a specific query with the ORM to add the collection of users linked to the occupation id

[@antoinedtube]

Hi Teddy, when we separate the models into their own DLL (with other linked classes and other stuffs), we can't reference those dll between them to avoid circular dependencies. Then how to make those many-to-many relationships because the reference would be on only one side?

[@busraucar2225]

Hello Teddy. I have a question. Thanks to EF, isn't it also done without creating any binding classes in many to many relationships? I mean, in Poker class: ICollection Categories is written, in Category class ICollectionPokers is written, won't a cross table be created automatically? Do we need to create binding class?

[@TeddySmithDev]

The new EF does everything for you now. When I created this video that feature did now exist.

[@busraucar2225]

@@TeddySmithDev Thanks for your response😊

[@witChaos]

Hello Teddy. I've a question. If somoene has two countries, for example he is half Spanish half Greek, is considered as a many to many relationship?

[@TeddySmithDev]

Interesting question. Yes that would be one to many. You could even have separate table for country based data if you want.

[@witChaos]

@@TeddySmithDev one to many or many to many I'm confused 😅

[@Saibandija]

@@witChaos This is my guess, but he probably meant many to many. A country can hold **one or many** persons, and a person can belong to **one or many** countries, therefore many to many. Though I think what you are actually referring to is a person's ethnicity rather than a country, in that case country (where you currently live) would have a one-to-many relationship with person and you could have another property for ethnicity (many to many).

[@weston4412]

So all the join classes aren't necessary if we know how to join data from different tables in SQL?

[@JonopolyHD]

Is there much difference between a Join Table and a View?

[@diegosabaris4282]

very useful video, thank you very much! one question, if a pokemon can have one owner at a time, doesn't it make it a one to many relationship, rather than a many to many?

[@HiroShinji22]

I admit I don't get the many-to-many relationship owners with pokemons. Here, a pokemon have a name and a birth date, like "Pikachu". It's more like an unique person. And Pikachu belongs to Sacha only. Pikachu can't belong to Pierre or I don't know. It will always be "owners" who can have multiple "pokemons".

[@Molecular_Machine]

Is there a love button. Mate, the like button is not enough to appreciate your great demonatration!

[@nuc1earant]

WARNING! BEFORE WATCHING THIS COURSE U NEED TO WATCH ALL SEASONS AND EPISODES OF POKEMON

[@TeddySmithDev]

🧢

[@nuc1earant]

@@TeddySmithDev aint no cap guys im fr. If u wanna understand go become a pokemon guru

[@learnffs-pl9ie]

Good thing you used squirtle as example. Vaporeon would be weird.

[@TeddySmithDev]

Squirtle is the best. Vaporeon sounds like a vape store.

[@learnffs-pl9ie]

@@TeddySmithDev oh you dont know vaporeon copypasta ?

[@TeddySmithDev]

Omg just googled lmao. U crazy 🤣🤣🤣

[@ishanillangakoon178]

Hi I would like to know how to identify one-to-one, one-to-many and many-to-many relationships using UML diagram ?

[@TeddySmithDev]

Look for fork and where lines connect. If there are forks on both side = many to many. If only one fork, one to many

[@ishanillangakoon178]

@@TeddySmithDev Thank You So much ! 👍

[@chadgregory9037]

Would this be done entirely differently if we were using view models instead?

[@enricoroselino7557]

so why do we use ICollection here not List ? funny thing is the same question when i started watch MAUI lesson with ObservableCollection instead of list

[@doointhedoo]

Teddy, I need to join two tables that are represented by two data model files in a Web API. how is this represented in the controller, the interface, and the repository?

[@caglarcansarikaya1550]

Thanks taddy I got this :) I have one another interesting question how should you implement a baby sitter in this. Baby sitter and pokemonowner are users, this is their role. Each owner has pokemon btw 0 to n, and also each baby sitter has a pokemon btw 0 to n. How should you create ?

[@chadgregory9037]

1:20 team rocket says bull fucking shit!!

[@chadgregory9037]

My shits unable to determine the relationship between entities on my many to many

[@mlbb_bros4659]

ur cutie-pie

[@instadop]

HOT 🥵

[@awaisnazir5983]

brother doing well, but let me give you an suggestion, try to make video short one, students dont have much time to watch lengthy videos, talk less and work more 🙂

[@TeddySmithDev]

Thanks you for commenting!

[@garshafatemianaraki9041]

Km

[@justaDN96]

need discord inv pls

[@TeddySmithDev]

discord.gg/ngatUdPMd6

[@randyrivera2660]

Thank you so much for this man 🫶