Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@openjpa.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Sat, 15 May 2010 02:01:04 -0700 (PDT)
From: vld <knezevicvladimir@yahoo.com>
To: users@openjpa.apache.org
Message-ID: <1273914064092-5058586.post@n2.nabble.com>
In-Reply-To: <02a601caf405$c33b55e0$49b201a0$@com>
References: <1273875529751-5057450.post@n2.nabble.com>
 <02a601caf405$c33b55e0$49b201a0$@com>
Subject: RE: Abstract class Fetch Join
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


crispyoz wrote:
> 
> I a have similar "Active" field on all my entities, I use "join fetch" not
> "left join fetch" for the same purpose but don't have this issue.
> 


Thank you for your reply.

I tried JOIN FETCH (although I can have LegalEntitys without address), but
the result is the same. Since I can't put an alias for JOIN FETCH
relationship, generated query contains two JOIN statements between
LegalEntity and Address, one for Fetch and one for Where.

It seems that
- SELECT le, a FROM LegalEntity le JOIN le.addresses a WHERE le.id=:id AND
a.isActive=true 
would solve the problem, but inheritance is not properly handled.

-- 
View this message in context: http://openjpa.208410.n2.nabble.com/Abstract-class-Fetch-Join-tp5057450p5058586.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.