How did you solve this? Are you setting the hibernate version to 2. To manually edit the hbm-files is not an option! Regards Niklas. Posted: Tue Jan 25, pm. All rights reserved. FAQ Search. Page 1 of 1. Previous topic Next topic. We saw that we will delete the referenced records of a particular record when we use delete cascade automatically.
Now, we will see how we can delete only specific child nodes or only some of the referenced records of the main record with the help of cascading but before that we will see how this can be done without using cascading. Now when we delete the subjects with id 56 and 57 only related to a particular department then we can do so by simply using cascade option of delete-orphan value.
Cascading can be done and enabled in either ways in hibernate. By using XML mapping file or by using annotations. We need to declare the cascade in the relationship variable in the XML mapping file of our hibernate project. When using annotations you can make use of Cascade annotation and mention CascadeType. If you want to mention multiple Cascade operations, you can do so by specifying them in a comma-separated string. In this way, cascading makes it easy and automatic to enable the functionality and operations for the referenced objects without writing special lines of code for it.
However, you should be careful while using Cascade as this could result in unexpected behavior when not wanted. But they get deleted because setting the cascade to all. So, be careful while using cascading. I have mapped the relation with a cascade attribute of "all-delete-orphan". Anyone knows how to solve this?
BuZZ-dEE 4, 9 9 gold badges 55 55 silver badges 80 80 bronze badges. Pablo Fernandez Pablo Fernandez You probably should show the relevant parts of your mappings. I use all-delete-orphan all the time with not-null foreign keys and have never had a problem. Add a comment. Active Oldest Votes.
GetEnumerator ; childEnumerator. Current; p. Remove c ; c. Flush ; will not remove c from the database; it will only remove the link to p and cause a NOT NULL constraint violation, in this case. Remove c ; session. Delete c ; session. Flush ; Now, in our case, a Child can't really exist without its parent. Sound advice from Gavin made me realise that my child entity class requires a link to the parent class via a many-to-one mapping.
Many thanks Ashoknan and Gavin! All rights reserved. FAQ Search. Page 1 of 1.
0コメント