Thank you for this video and explanation of the mappings. It is by far the best for me to understand with code example. Quick and easy, not boring at all, right to the point.
Regarding many-to-many, normally you would like to reuse the item rows when several customers share a same item. Thus the cascade type should not be ALL. Otherwise when you remove a customer, all its items will be removed as well, which makes sense in the case of one-to-many but not many-to-many (and many-to-one).
Explanation is too fast. All the relationships are explained in one video in short time and couldn't able to understand. Appreciate if you can do one each relational mapping with example and showing DB changes along with the code.
Unidirectional Relationships:- 1. Unidirectional is a relation where one side does not know about the relation. 2. In a unidirectional relationship, only one entity has a relationship field or property that refers to the other. For example, Line Item would have a relationship field that identifies Product, but Product would not have a relationship field or property for Line Item. In other words, Line Item knows about Product, but Product doesn’t know which Line Item instances refer to it. Bidirectional Relationships:- 1. Bidirectional relationship provides navigational access in both directions, so that you can access the other side without explicit queries. 2. In a bidirectional relationship, each entity has a relationship field or property that refers to the other entity. Through the relationship field or property, an entity class’s code can access its related object. If an entity has a related field, the entity is said to “know” about its related object. For example, if Order knows what Line Item instances it has and if Line Item knows what Order it belongs to, they have a bidirectional relationship.
How to update foreign key with new primary key ??? My query is "update Card o Set o.customer.userName=:newuserName where o.customer.userName=:userName";
Thank you for this video and explanation of the mappings. It is by far the best for me to understand with code example. Quick and easy, not boring at all, right to the point.
Regarding many-to-many, normally you would like to reuse the item rows when several customers share a same item. Thus the cascade type should not be ALL. Otherwise when you remove a customer, all its items will be removed as well, which makes sense in the case of one-to-many but not many-to-many (and many-to-one).
Thank you so much for this video. The concepts are explained in a very detailed manner. This helped me a lot. May God bless you !
Excellent. Thanks for sharing your knowledge. Greetings from Perú.
Nice explanation bro.... thank you
Really useful to understand the entity annotations. Thanks!
for aan example of bidirectional one t one when the get all is called on referencing entity it goes in infinte loop, not sure you face same issue
Many thanks!
All type of relations worked for me
Great! thanks for covering all in single video
Don't worry man. Subscribed. Keep going. There's very little about entity mappings on RUclips.
finally some decent explanation.
Thanks
Recommended
Great explanation... Thank you
Thanks for the video
bro , you rock !
clear cut explanation,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,...............................................
Explanation is too fast. All the relationships are explained in one video in short time and couldn't able to understand. Appreciate if you can do one each relational mapping with example and showing DB changes along with the code.
Thank you. Very nice explanation.
Thanks a lot very clear :)
Thanks mate ! i need this video
Nice explanation...and thank you so much
Hi, thanks for the video, would you mind explaining when to go with unidirectional, bidirectional & Join table
Unidirectional Relationships:-
1. Unidirectional is a relation where one side does not know about the relation.
2. In a unidirectional relationship, only one entity has a relationship field or property that refers to the other. For example, Line Item would have a relationship field that identifies Product, but Product would not have a relationship field or property for Line Item. In other words, Line Item knows about Product, but Product doesn’t know which Line Item instances refer to it.
Bidirectional Relationships:-
1. Bidirectional relationship provides navigational access in both directions, so that you can access the other side without explicit queries.
2. In a bidirectional relationship, each entity has a relationship field or property that refers to the other entity. Through the relationship field or property, an entity class’s code can access its related object. If an entity has a related field, the entity is said to “know” about its related object. For example, if Order knows what Line Item instances it has and if Line Item knows what Order it belongs to, they have a bidirectional relationship.
@@technotowntechie9732 can you please explain littel bit more about point1.
just confused about --> other side without explicit queries.
Good job man!
Thanks nice explanations
Nice and very well explained.
Great video! One question: why do you change from List to Set?
avoid to duplicate data 's
Helpful
Thank You So Much
2 schemes created in myself?
Great explanation! But the video's sound is very poor, barely able to hear the voice on the laptop.
Sorry about that Achyut.
Yes vidio content is great ..but please improve the sounding....cheers✌
Seems like running fastly to cover the topics, if you do in slow way it will be easily understandable to all
How to update foreign key with new primary key ??? My query is
"update Card o Set o.customer.userName=:newuserName where o.customer.userName=:userName";
upgrade ur micrphne.... thats y indian utubers r nt gettng any lights...
Sure, Thank You
boooring explanatioon
Thanks 😊
Very boring
Thank You