[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-2164) Minor bug in section "20.1.1. Customizing the schema"

[Diego Pires Plentz (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Diego Pires Plentz resolved HHH-2164.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.3

> Minor bug in section "20.1.1. Customizing the schema"
> -----------------------------------------------------
>
>                 Key: HHH-2164
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2164
>             Project: Hibernate3
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.2.0.ga
>            Reporter: Andres Gonzalez
>            Assignee: Diego Pires Plentz
>             Fix For: 3.3
>
>   Original Estimate: 1 minute
>  Remaining Estimate: 1 minute
>
> Where it says:
> *******************************************************************************************************************************
>  A unique-key attribute may be used to group columns in a single unique key constraint. Currently, the specified value of the unique-key attribute is not used to name the constraint in the generated DDL, only to group the columns in the mapping file.
> <many-to-one name="org" column="orgId" unique-key="OrgEmployeeId"/>
> <property name="employeeId" unique-key="OrgEmployee"/>
> *******************************************************************************************************************************
> i think the unique-key attributes should jave both the same value ("OrgEmployee", for example)

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