[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5406) Schema export does not consistently follow naming strategy for unique constraints

[Jonathan (JIRA)]

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

Jonathan commented on HHH-5406:
-------------------------------

I noticed that this issue also effects other annotations, such as @Index. For example, given this entity:

@Entity
class MyEntity {
@ManyToOne
EthernetPort ethernetPort;
int instanceId;
}

Using the ImprovedNamingStrategy I should be able to create an index like this:

@Index(name = "idx", columnNames = { "ethernet_port", "instance_id" })

but Hibernate only allows this:

@Index(name = "idx", columnNames = { "ethernet_port", "instanceId" })



> Schema export does not consistently follow naming strategy for unique constraints
> ---------------------------------------------------------------------------------
>
>                 Key: HHH-5406
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5406
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.4
>         Environment: Hibernate 3.5.4, No database needed
>            Reporter: Jonathan
>            Priority: Minor
>         Attachments: UniqueConstraintTest.java
>
>
> When performing a schema export for entities that include annotated unique constraints, Hibernate does not consistently follow the naming strategy for field names in the unique constraint. It appears that a naming strategy applies only for fields that are mapped to another class. The attached test demonstrates this.

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