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

preview_player
Показать описание
ASP.NET Core Web API .NET 6 2022 - 3. One-To-Many Relationships

Рекомендации по теме
Комментарии
Автор

Truly grateful for the selfless sharing by the author, who is truly a great disseminator of technology. Thank you.

旷野中的小草
Автор

Thanks again! Finished your C# course and progressing in this!

dq
Автор

Hi Teddy, thanks for this series of tutorials. I enjoyed and actually learnt a lot regarding your UML Diagram. I'm following this til the end.

mbulelo-damba
Автор

love you Teddy! Last week i simply just searched keyword like java and you bring me to the new world. I have a similar background as you and i get really confused how can i break into the industry. After that i watch every your video, starting to learn C#. This video explaination is amazing because you can visual the complicated relationship and tell in a smooth way. So i cannot just watch the video and go away. You re really crazy man. it seems that you make video every day and burning yourself. Please take a rest man! you work really really hard! and this video is really good, escpecially the parts of key and relationship. i will keep going and follow your track :D i really appreciate you!!!

leafmagi
Автор

Boosting your videos for the algorithm, great video on relational databases.

justadude
Автор

Dude after watching sooo many tutorials from developers from India.... listening yours is sooo much cool lol

HoopersHighlights-lz
Автор

Started my journey as a self taught back-end dev recently and i can say the videos up to now are amazing.I am sure to stick around until the end.Mind me asking also if there is a chance that you do a short tutorial about Git

dzaninkudus
Автор

Hey Teddy great video overall, but I would argue against your comments around 8:40 where you state that an ICollection is not editable. IEnumerable is not editable, but ICollection is derived from IEnumerable and includes additional functionality to add/remove/update elements in the list. Similarly, you state that ICollection will ALWAYS be used in one-to-many relationships for the many.. IEnumerable is also another very popular way to handle one-to-many. Maybe I'm misguiding, so I would love to hear your take on this.

kuhlektv
Автор

I guess you are telling it all reverse. For those having confusion in this one-many or many-one relationship, look at some ER daigram examples.

Pokemon table is the 'one' endpoint and Review table is the 'many' endpoint i.e. one Pokemon can have many review.

We have ICollection in Pokemon table because One Pokemon can have multiple reviews and thats why we need something to hold list of reviews.

We have simple Pokemon field in the Review table because one review contains details about a single Pokemon

Kaivalyamani
Автор

As I'm doing this in my current app, I find myself saying it just like Teddy and moving the mouse, "One...to many...one...to many" lol :D Thanks Teddy.

muttBunch
Автор

Bro really helpfully videos
Im trying switch from node js to c#
Im frontend react dev
But find job on fullstack. My firrst app on node js was todo. I'm was so impressed such simple app is can't find examples on YouTube
Your cours is a masterpiece!
Thanks for sharing. Its really helpful!
Best regards!

yankov
Автор

Definitively agree on the Django Models comment, kinda interesting sometimes XD

sdscode
Автор

Thanks man I understood how to write code for relationships after 2days from searching .

HussainAl-ahmdi
Автор

Bro...I love your tutorials but 10:01 ...not true...I've worked in Flask with SQLAlchemy and the Model definitions are bliss and relationships are easy one-liners. easier and cleaner in Python...The only reason I'm learning C# now is because my company builds their API's in C# so I need to up my C# game but would be way less code with Python, Flask and SQLAlchemy...can't comment on Django as I've not used it but if it supports SQLAlchemy I assume it would be similar. Here's an example. I have a CoinInfo model in which the symbol_id is a Foreign Key for a table called TickerData. I don't have to have 3 locations to define this connection (like in the many-to-many you need to add some lines in the Primary table, the Ref table and the DataContext class).
```python
class CoinInfo(db.Model):
id = db.Column(db.Integer, primary_key=True, autoincrement=True)
symbol_id = db.Column(db.Integer,
insert_timestamp = db.Column(db.DateTime, default=datetime.utcnow())
update_timestamp = db.Column(db.DateTime, default=datetime.utcnow(), onupdate=datetime.utcnow())

ticker_data = db.relationship('TickerData', backref='coin_info', uselist=False)
```

andreibudaes
Автор

I am confused, Upon setting public Country Country { get; set; } ( @9:14 ) I get Country is a namespace but used like a type.

RAMATW
Автор

1:1 basically like having a complex datatype as an entity field.

chadgregory
Автор

Hi Teddy, thank you for all this content. I just got one quick question. According to what I saw in Many To Many rels video, we don't need to specify, for example, the country_id field in Owner's model? Because you are referencing the relationship itself but we are not specifying the country_id field.

joaquincataldo
Автор

Can I use Mysql instead sql server for doin this?

EdgarDanielLópezCarbajal
Автор

Would you add the ? after string for nullable fields?? i.e. public string? Name { get; set; }

cryptoeric
Автор

Hi can you make like a project with dal bal layer with like calling stored procedure also using azure please 😢😢😢😢😢😢

random-bdxg