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 (JIRA)" <ji...@apache.org> on 2012/10/01 21:09:08 UTC

[jira] [Reopened] (OPENJPA-2247) JoinColumn annotation is ignored when mapping a unidirectional owned OneToOne that is in a SecondaryTable

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

Albert Lee reopened OPENJPA-2247:
---------------------------------

      Assignee: Albert Lee  (was: Rick Curtis)

Reopen the issue to address similar problem affecting the 1x1 bi and mx1 uni use case.
                
> JoinColumn annotation is ignored when mapping a unidirectional owned OneToOne that is in a SecondaryTable
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2247
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2247
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Rick Curtis
>            Assignee: Albert Lee
>             Fix For: 2.3.0
>
>
> The runtime incorrectly ignores @JoinColumn.name when mapping a unidirectional owned OneToOne that is in a SecondaryTable.
> This problem only exists when running with a persistence.xml that is set to 2.0 (version="2.0">).
> For example:
> @Entity
> @SecondaryTable(name = "ParentSecondaryTable", pkJoinColumns = 
>     { @PrimaryKeyJoinColumn(name = "idParent", referencedColumnName = "idParent") })
> public class Parent {
>     @Id
>     @GeneratedValue
>     int idParent;
>     String child_ref;
>     @OneToOne
>     @JoinColumn(name = "CHILD_REF", table = "ParentSecondaryTable", referencedColumnName = "idChild")
>     PChild child;
> }
> The column "CHILD_REF" will be ignored and the runtime will look for the fk in non-existent column ParentSecondaryTable.CHILD_IDCHILD.

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