Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1110927655.1246627487566.JavaMail.jira@brutus>
Date: Fri, 3 Jul 2009 06:24:47 -0700 (PDT)
From: "Ashish Paliwal (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-1128) Collocation constraint in case of
 OneToOne unidirectional Eager join.
In-Reply-To: <562993557.1244403187350.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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-TEST-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-2.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.