The following comment has been added to this issue:
Author: Emmanuel Bernard
Created: Mon, 5 Jan 2004 4:15 PM
Body:
Actually there is a mismatch between a not-null column and a not-null property. Hibernate is probably missing the first concept.
Checks could be done in the JAVA level for <subclass> properties.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-602
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-602
Summary: hbm2ddl create unexpected not-null constraints on <subclass>
Type: Bug
Status: Closed
Priority: Minor
Resolution: WON'T FIX
Project: Hibernate2
Components:
core
Versions:
2.1.1
Assignee:
Reporter: Emmanuel Bernard
Created: Mon, 5 Jan 2004 10:37 AM
Updated: Mon, 5 Jan 2004 4:15 PM
Description:
When declaring not-null property into <subclass> A and not in it's superclass (SuperA), then SuperA cannot be insert (constraints violation).
This is not expected.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
