@ManytoMany with join table and @CollectionOfElements : conceptual difference
posted 5 years ago
I need some conceptual explanations from you gurus:
I was designing an entity bean and this entity "UserType" has a relationship with Questions so i had a join table where I had the relationship for the two and an extra column defining the order of the questions (Table: UserTypeId , QuestionID , Order):
Firstly as I would always use I used @manytoMany like this :
what happened in this one was that when ever I tried to use EntityHome.remove() ( this is a jboss seam's component which only calls the entitymanager's remove method and some message methods ) what it would do is try to put null in the UserTypeId column ( in the join table) which cannot be null it did not remove the whole row as it should. The other way would have been to fire a native sql query which was not a good solution. Just to explain, I was not doing a delete on the question object because it was just a part of the join table so what I did was to query the object that depicted the whole row of the join table with the "ORDER" field and a composite primary key ((UserTypeId and QuestionId) and Order) and then did a remove on that which was the way one deletes any row form the table. Right?
SO... I was advised to use this instead:
this one works perfect, Now as per my concepts the one with @ManytoMany should work as well. but it didnt. My question here is why? why it did not work. and Why does this one works. I have put this annotation and its working but i want to understand why is this one working. now I remove anything from the list and the remove is automatically triggered to the table as well.
I will really appreciate the answers and explanations.
Thanks in advance.
posted 5 years ago
no one !!!
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads