[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3898?page=c... ] Francisco Peredo commented on HHH-3898: --------------------------------------- IMO hibernate.check_nullability should default to false (so that it is JPA compatible by default) and if not it should be documented with big bold letters, org.hibernate.engine.Nullability.checkNullability is a major problem if you want to validate newly persisted objects when the transaction ends. I still think that adding support for the "optional=true and nullable=false" (see my comment in my blog: http://luxspes.blogspot.com/2009/11/jpa-myth-eclipselink-and-hibernate-ar...) solution would have been much more flexible (I would have allowed to turn on/off org.hibernate.engine.Nullability.checkNullability on a "individual property" basis) -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3898?page=c... ] Emmanuel Bernard commented on HHH-3898: --------------------------------------- it would have been better but it also woud break existing user apps if we decide to go that route now and we don't want that if that's avoidable. -- 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