[hibernate-issues] [Hibernate-JIRA] Moved: (HHH-2199) Unique constraints on nullable columns should not be generated with unique-key is used and supportsNotNullUnique=false

Emmanuel Bernard (JIRA) noreply at atlassian.com
Mon Oct 30 20:54:04 EST 2006


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2199?page=all ]

Emmanuel Bernard moved ANN-481 to HHH-2199:
-------------------------------------------

        Project: Hibernate3  (was: Hibernate Annotations)
            Key: HHH-2199  (was: ANN-481)
      Component: metamodel
                     (was: binder)
    Fix Version: 3.2.1
                     (was: 3.2.1)
        Version: 3.2.0.ga
                     (was: 3.2.0.ga)

> Unique constraints on nullable columns should not be generated with unique-key is used and supportsNotNullUnique=false
> ----------------------------------------------------------------------------------------------------------------------
>
>          Key: HHH-2199
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2199
>      Project: Hibernate3
>         Type: Bug

>   Components: metamodel
>     Versions: 3.2.0.ga
>     Reporter: Emmanuel Bernard
>     Assignee: Emmanuel Bernard
>      Fix For: 3.2.1

>
>
> Derby and the DB2 family suffers from it.
> This limit the user ability to have a portable mapping

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




More information about the hibernate-issues mailing list