[hibernate-issues] [Hibernate-JIRA] Created: (HHH-5089) not-null integrity must be checked for DML statements and not for objects

[Markus Bohr (JIRA)]

not-null integrity must be checked for DML statements and not for objects
-------------------------------------------------------------------------

                 Key: HHH-5089
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5089
             Project: Hibernate Core
          Issue Type: Bug
          Components: core
    Affects Versions: 3.3.1
         Environment: Windows XP
Eclipse 3.5.1
Teneo 1.0.3
            Reporter: Markus Bohr


This issue somehow relates to HHH-4057 but is of much broader scope and pointing out a different aspect.

Currently Hibernate checks the not-null constraint integrity persisting any object already on the object level (which is a quite early point in time; for loading objects, this might cause analoguous problems).

The not-null XML attribute, however, is part of the <column> tag and therefore is assumed to match the characteristics of a column and not a mapped object property!
I am facing severe problems with the current behaviour, as the not-null check is performed even before 
any nullSafePut() method is executed for a customized Hibernate type, or even before any the any PreInsertEventListener / PreUpdateEventListener has a chance to transform null-values for properties to non-null values for database columns.
Effectively, the flexibility to handle different nullability characteristics between columns and their mapped properties is thus reduced to zero.

-- 
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