[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-2686) Include a primary key in the sequence table used by id.enhanced.TableGenerator

[Steve Ebersole (JIRA)]

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

Steve Ebersole updated HHH-2686:
--------------------------------

         Assignee: Steve Ebersole
    Fix Version/s: 3.3.x

Thanks for the patch Matt.  Mostly likely that will not be the solution though since it makes assumptions wrt how one can create a table's primary key which is dialect specific.  Probably I should have just "done this correctly' and used o.h.mapping.Table from the start.  I'll make that change, and add the o.h.mapping.PrimaryKey reference at the same time.

Is it specifically the INDEX for which you are looking?

> Include a primary key in the sequence table used by id.enhanced.TableGenerator
> ------------------------------------------------------------------------------
>
>                 Key: HHH-2686
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2686
>             Project: Hibernate3
>          Issue Type: Improvement
>    Affects Versions: 3.2.3
>         Environment: Mac OS X (Intel) 10.4.9, Java 1.5.0_07, Hibernate 3.2.3.ga, MySQL 5.0.24a
>            Reporter: Matt Solnit
>            Assignee: Steve Ebersole
>            Priority: Minor
>             Fix For: 3.3.x
>
>         Attachments: TableGenerator.java.diff
>
>
> It would be great if the new TableGenerator used a primary key on the "sequence_name" column.  This would most likely improve performance when you have a large number of "sequences" in the table.  I attempted to provide a patch :-).

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