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

Posted to dev@openjpa.apache.org by "Ashish Paliwal (JIRA)" <ji...@apache.org> on 2009/07/01 15:57:47 UTC

[jira] Updated: (OPENJPA-1128) Collocation constraint in case of OneToOne unidirectional Eager join.

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

Ashish Paliwal updated OPENJPA-1128:
------------------------------------

    Attachment:     (was: OPENJPA-1128-1.patch)

> Collocation constraint in case of OneToOne unidirectional Eager join.
> ---------------------------------------------------------------------
>
>                 Key: OPENJPA-1128
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1128
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: slice
>    Affects Versions: 2.0.0
>         Environment: Windows, openjpa 2.0.0
>            Reporter: Ashish Paliwal
>             Fix For: 2.0.0
>
>         Attachments: OPENJPA-1128-TEST-1.patch, Relaxing_the_Collocation_Constraint.pdf
>
>
> In case of OneToOne eager unidirectional join, collocation constraint holds currently. This means, say we have 2 entities Person and Address, then both Person and its related address needs to be in the same slice. 
> This feature is to remove this restriction in case of OneToOne eager unidirectional join.

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