[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3650) TableGenerator doesn't marks the "primary key" as not null, causing errors in some RDBMS's which expects the PK to be not-null

[Steve Ebersole (JIRA)]

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

Steve Ebersole commented on HHH-3650:
-------------------------------------

Juca, why was this not applied to the 3.2 branch?

> TableGenerator doesn't marks the "primary key" as not null, causing errors in some RDBMS's which expects the PK to be not-null
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HHH-3650
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3650
>             Project: Hibernate Core
>          Issue Type: Patch
>          Components: core
>         Environment: DB2v82 and Branch_3_3 and trunk
>            Reporter: Juraci Paixao Krohling
>            Assignee: Juraci Paixao Krohling
>             Fix For: 3.3.x, 3.5
>
>         Attachments: TableGenerator.java.diff
>
>
> Some RDBMS's requires that the primary key columns be not-null. This causes some tests which relies on the org.hibernate.id.enhanced.TableGenerator to fail on error. The attached patch adds the string "not null" to the table creation statement. 

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