Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of awhite@bea.com designates
 63.96.162.5 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <864cafc0608201546h4efad3b5jaf0e947f6d6b7b30@mail.gmail.com>
References: <864cafc0608201546h4efad3b5jaf0e947f6d6b7b30@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6BE16EA1-F9C2-4C6A-87DF-F295B8C2E39E@bea.com>
Content-Transfer-Encoding: 7bit
From: Abe White <awhite@bea.com>
Subject: Re: openjpa eager subclass fetching
Date: Mon, 21 Aug 2006 09:25:46 -0700
To: open-jpa-dev@incubator.apache.org

> Since the subclass data is in the same table as the base table being
> queries,  shouldn't this
> data be retrieved with a single select automatically ?

Yes, it should be fetched by default.  Unless of course all your  
subclass fields set their fetch mode to LAZY or are to-many relations  
that would be LAZY by default.

Have you updated your OpenJPA view recently?  I remember fixing some  
bugs surrounding subclass fetching a while ago (maybe 10 days  
ago?).   They had slipped in during the recent implementation of  
fetch depths.
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.