You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Albert Lee (Updated) (JIRA)" <ji...@apache.org> on 2012/02/02 20:34:54 UTC

[jira] [Updated] (OPENJPA-793) Embeddables does not work properly with duplicate persistent field names

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

Albert Lee updated OPENJPA-793:
-------------------------------

    Fix Version/s:     (was: 2.2.0)
                   2.3.0

Moved fix version to 2.3.0 in preparation for 2.2.0 release.
                
> Embeddables does not work properly with duplicate persistent field names
> ------------------------------------------------------------------------
>
>                 Key: OPENJPA-793
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-793
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Fay Wang
>            Assignee: Fay Wang
>             Fix For: 2.3.0
>
>         Attachments: openjpa-793-1.patch, openjpa-793-3.patch, openjpa-793-testcase.patch, openjpa-793.patch
>
>
> If an embeddable has the same persistent field names as its owning class, or two embeddables contains the same field names and both are embedded in an entity class, openjpa will not work properly due to the column name clashes. The fix is for openjpa to detect these situations and throw an exception and for the application to use @AttributeOverride to specify unique column names for the persistent fields in the embeddable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira