You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Marc Logemann (JIRA)" <ji...@apache.org> on 2012/11/11 12:13:12 UTC

[jira] [Commented] (OPENJPA-1541) Support Enum as Primary Key Type

    [ https://issues.apache.org/jira/browse/OPENJPA-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494857#comment-13494857 ] 

Marc Logemann commented on OPENJPA-1541:
----------------------------------------

I am still missing this feature heavily. Especially for Configuration Tables this would be really nice. Otherwise people continue to use static Strings as keys. old-school.
                
> Support Enum as Primary Key Type
> --------------------------------
>
>                 Key: OPENJPA-1541
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1541
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: competitive, jpa
>    Affects Versions: 2.0.0-beta
>         Environment: All
>            Reporter: bernard
>            Priority: Critical
>
> Enums work as primary keys in TopLink and EclipseLink. DataNucleus supports them, too:
> http://www.datanucleus.org/products/accessplatform/jpa/primary_key.html
> It would be good to also include this in the specification because, not to support type safety in primary keys is fairly sad.
> Enum is a basic language feature, and most applications would enjoy significant benefits by mapping the keys of those little system behavior controlling lookup tables to enums.
> Consider a payment_type table. One can only generate the IDs of the table and use them for switching safely when the ids are mapped to enums. Any such application would typically have a PaymentType enum anyway.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira