HHH-8273 Incorrect "unique-key" naming comment in docs

This commit is contained in:
Brett Meyer 2013-05-25 20:29:09 -04:00
parent 7fad06da4a
commit 8f07d59243
2 changed files with 4 additions and 7 deletions

View File

@ -522,9 +522,8 @@
The <option>not-null</option> and <option>UNIQUE</option> attributes generate constraints on table columns.
</para>
<para>
The unique-key attribute groups columns in a single, unique key constraint. Currently, the specified value
of the unique-key attribute does not name the constraint in the generated DDL. It only groups the columns in
the mapping file.
The unique-key attribute groups columns in a single, unique key constraint. The attribute overrides
the name of any generated unique key constraint.
</para>
<programlisting language="XML" role="XML"><xi:include href="extras/notnull-unique.xml" xmlns:xi="http://www.w3.org/2001/XInclude" parse="text" /></programlisting>
</step>

View File

@ -95,10 +95,8 @@
<para>
A <literal>unique-key</literal> attribute can be used to group columns in
a single, unique key constraint. Currently, the specified value of the
<literal>unique-key</literal> attribute is <emphasis>not</emphasis> used
to name the constraint in the generated DDL. It is only used to group the columns in
the mapping file.
a single, unique key constraint. The attribute overrides
the name of any generated unique key constraint.
</para>
<programlisting role="XML"><![CDATA[<many-to-one name="org" column="orgId" unique-key="OrgEmployeeId"/>