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

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

Thank you, Teddy. Your explanations are precise.

Thanks again, Teddy! Keep up the good teaching!

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

Thank you for your great videos, Teddy

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!

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

Teddy good work! One possible procedure how to create more complex data structures is to create it on MS SQL server (with SQL Server management studio - SSMS) and create Database diagram, where you can see visually how the tables are joined. If you are satisfied, you can use Scaffold-DbContext command to generate model. You can make changes in the model and then migrate changes to the same (other) database through Add-Migration and Update-Database. Your changes can be seen in database diagram in SSMS. It is good to see what exactly is in database visually, I think.

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

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

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

Thanks, Teddy! From your subscriber from Uzbekistan!

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

Thank you bro, you're my hero

Great Pokemon explanation of many to many

Great, I learned a lot about relationships and keys.

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

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

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 ?

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

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

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?

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?

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?

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

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

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

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?

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?

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

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

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

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

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".

1:20 team rocket says bull fucking shit!!

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

ur cutie-pie

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 🙂

need discord inv pls

Thank you so much for this man 🫶