You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2009/08/19 18:13:14 UTC

[jira] Updated: (OPENJPA-1061) Entities extending from a Mapped Superclass that defines the ID fields share the same ObjectID type parameter

     [ https://issues.apache.org/jira/browse/OPENJPA-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated OPENJPA-1061:
----------------------------------

    Fix Version/s:     (was: 2.0.0)
                   2.0.0-M3

> Entities extending from a Mapped Superclass that defines the ID fields share the same ObjectID type parameter
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1061
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1061
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 1.2.0, 1.2.1
>            Reporter: Jody Grassel
>            Assignee: Michael Dick
>             Fix For: 1.2.2, 1.3.0, 2.0.0-M3
>
>         Attachments: OpenJPA-1061_1.2.x.patch, OpenJPA-JIRA1061-packagerefactor-1.2.x.patch, OpenJPA-JIRA1061-packagerefactor-trunk.patch, OpenJPA-JIRA1061_1166-packagerefactor-1.2.x.patch
>
>
> When a mapped superclass (MSC) defines @Id fields, it appears that entities extending the MSC use the MSC's type in the generated ObjectID's type field.  This can result in unexpected primary key collissions between entities that are not intended to be related in an entity inheritance hierarchy.  Attached to the JIRA is a junit test case that demonstrates the problem. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.