[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2792) Session.delete is validate all fields are null

[Shawn Clowater (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31895#action_31895 ] 

Shawn Clowater commented on HHH-2792:
-------------------------------------

Ok, the search feature of JIRA does work as I was about to raise the same issue.

It seemed very strange to me that the delete event would bother to check the nullability on a column on an entity that is being deleted.  In my case the problem is user induced.  They're working with an object, update it in a detached state and then decide to throw away the whole record.  I've told them to 'not do that' for the short term but is there any reason that nullability check needs to be there or is it just a copy/paste sort of behavior form the update/insert events.

> Session.delete is validate all fields are null
> ----------------------------------------------
>
>                 Key: HHH-2792
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2792
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>            Reporter: Daniel Passos
>
> session.delete operation would not have to validate if the fields are null
> The problem in DefaultDeleteEventListener.deleteEntity -> Nullability.checkNullability

-- 
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira