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!

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

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

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

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

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

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

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.

Thanks, Teddy! From your subscriber from Uzbekistan!

Thank you bro, you're my hero

Great, I learned a lot about relationships and keys.

Great Pokemon explanation of many to many

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

5 ай бұрын

Cool name lol. Thanks for commenting!!!

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

2 жыл бұрын

This is really cool

@chadgregory9037

2 жыл бұрын

@@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

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

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

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?

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

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?

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?

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

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

10 ай бұрын

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

@busraucar2225

10 ай бұрын

@@TeddySmithDev Thanks for your response😊

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

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?

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

@TeddySmithDev

8 ай бұрын

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

@learnffs-pl9ie

8 ай бұрын

@@TeddySmithDev oh you dont know vaporeon copypasta ?

@TeddySmithDev

8 ай бұрын

Omg just googled lmao. U crazy 🤣🤣🤣

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

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

@TeddySmithDev

8 ай бұрын

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

5 ай бұрын

@@TeddySmithDev Thank You So much ! 👍

1:20 team rocket says bull fucking shit!!

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

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

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

@TeddySmithDev

7 ай бұрын

🧢

@nuc1earant

7 ай бұрын

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

ur cutie-pie

@naskett1784

4 ай бұрын

HOT 🥵

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

8 ай бұрын

Thanks you for commenting!

need discord inv pls

@TeddySmithDev

Жыл бұрын

discord.gg/ngatUdPMd6

Thank you so much for this man 🫶