Django Rest Framework API #19 / One To One Relationship, Nested Data

Django Rest Framework API #19,You Will Learn:
1- How to link two models using One To One relationship.
2- How get and show the nested data from the API response.
3- How to get the instance of the object that represent the nested data and save it by overriding the Create Action.
🎧 Music : • Study music | Programm...
Music Channel : @tuningthecode
Source code: github.com/CodeEnvironment/dj...
Override Create Action Inside ModelViewSet video:
www.youtube.com/watch?v=4dPVy...
Django Rest Framework API #22 / Many To Many Relationship , Nested Data:
• Django Rest Framework ...
Django Rest Framework API #16 / Many To One Relationship, Nested Data:
• Django Rest Framework ...

[@harrietly4932]

love the demo on postman where we can see the final data structure and relationship of post and rates models!

[@yarik83men51]

Thx

[@muhammadehtisham2708]

good one sir g .

[@rajas6710]

Excellent

[@brenoverissimo3846]

I was stuck in this part and you really helped me! Thanks!

[@codeenvironment]

I’m glad I could help 👍🏻

[@zakchips]

Thanks. Mostly we see OneToOne relationships in User - Profile. I use djoser to create a user object and signal to sync it with creation of a profile object. But you've shown an interesting example where we can use functionality of viewsets instead.

[@codeenvironment]

Thank you. Always try to avoid over engineering when possible.

[@muhammadehtisham2708]

very help full

[@oscarparedez1417]

Amazing job. Congratulations and thanks for the amazing tutorial!

[@codeenvironment]

Thank you for the support 👍🏻

[@akshay_pawar10]

Thank you for the wonderful tutorial. But I have a question regarding the update method, how can I update PostRate model along with Post model in same request.

[@SiddiqNx]

Good video brother. I have a doubt. You created the PostRates model with 2 fields. Why not add the post as OneToOne field in the PostRates model? In that way we can query the PostRates model later using the post_id instead of going through the Post model. Which one will be a better design? Another doubt is that do you think splitting the Post and PostRates model is better than just adding likes and dislikes field in the Post model? What is the use of splitting them when it just increases the number of lines of code to save the rates data?

[@codeenvironment]

Thanks Siddiq for the question. First doubt: you could do that, but then you will need to send two request to your API to get the post first and then the rates next and that is not a good approach especially when you have thousands of post. Plus you need more coding and effort in the frontend. Second doubt: adding likes and dislikes fields in the Post model is not wrong. but, splitting creates a better data and code structure ,helps with debugging and testing and makes your system more flexible cause you can link rates model with other models e.g( blogs, comments, articles ...etc) and actually you end up reducing the number of lines in your code.

[@SiddiqNx]

@@codeenvironment Thank you! Got it now. These design decisions come only with experience I guess.

[@LakshmanKumar-qp9xn]

Hi it's very nice. But how to create more than one , for one to one relationship ..

[@LakshmanKumar-qp9xn]

For example.. X class contains a, b, c, d, one to one relationship.. How to we have write create method in class based views... Please give me suggestion..

[@codeenvironment]

@@LakshmanKumar-qp9xn You can just create an object for each relational field ( a, b, ... c) like what I did at 10:40 and then add them to the main object.