Entity Mapping | @OneToOne, @OneToMany, @JoinColumn| Spring Data JPA | Spring Boot | Dev2Prod Coding

Great explanation 👌🏻😇

nice video!! +1 sub, thanks

if i duplicate my request in postman, so duplicate my entities, that not shoul be happen, because then i have duplicate employees and addresses, how do yo stop this behavior, you put some logical in your service?(sorry for my english)

bro dhanyawad

Bruh you did not even explain what is onetoone or anything.. worst explanation

fk_add_id is not reflecting in employee table. and no data in adreess table. pls help me

thank you

Where is properties file

Very Good Explained..Thank You.....

Awesome explanation. I hope you can make more videos.

short and clear. Thank you

You didn't even show how to right at the get mapping, so you just showed how to do the annotations, how is someone meant to known how to make the get request!!!

So good explained! Just one question, first OneToOne Example, in Entity Employee_Detail you add Address address, which created automatically a FK fk_add_id, should a index be created to that fk_add_id, if data volumn is very big? Thank you!

very helpful

Perfect explanation😊

I like the fact that you have already created the classes(entity, controllers) before you record the video, which makes the video simple and short

I might sound stupid but I found it interesting that f.k @OneToOne private Address address, Employee class has a attribute of address which data type is Address, and it actually stores int value which is addressID? and by setting cascade.all, when we send request payload for saving emps, it will affect Address class and save address info on Address table. And the fk column in emp table will show just int value(AddrID). I learned a lot. and I hope I understand correctly. Thanks!