[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4612?page=c...
]
Emmanuel Bernard resolved HHH-4612.
-----------------------------------
Resolution: Rejected
Hey, It's not conflicting. FK constraints work properly but NOT-NULL constraints can
cause issues and in this case delete ordering matters.
Confusing documentation for 10.8 order of object deletion
---------------------------------------------------------
Key: HHH-4612
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4612
Project: Hibernate Core
Issue Type: Bug
Components: core
Reporter: Chris Wilson
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
The Hibernate documentation (section 10.8. Deleting persistent objects) says:
"You can delete objects in any order, without risk of foreign key constraint
violations. It is still possible to violate a NOT NULL constraint on a foreign key column
by deleting objects in the wrong order, e.g. if you delete the parent, but forget to
delete the children."
These two sentences are conflicting. The first one says that you don't risk foreign
key constraint violations, the second one says that you do. The first one says that
deletion order is not important, the second one says that it is.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira