jsr338-experts@jpa-spec.java.net

[jsr338-experts] Re: outer fetch joins with on-conditions

From: Rainer Kwesi Schweigkoffer <kwesi_at_sap.com>
Date: Mon, 12 Nov 2012 13:16:37 +0100

Pinaki Poddar, am 8 Nov 2012 hast Du um 9:39 zum Thema "[jsr338-
experts] Re: outer fetch joins with on-co" geschrieben :

>
> > We also have a fetch-plan item on our agenda (which I hope to be able to
> address in this release, despite the tight timelines)
>
> I support that we explore fetch planning as an independent construct over
> the approach of augmenting JPQL to control the access pattern.
> A fetch plan as a subsidiary to find() or query operations will allow JPA
> to support more sophisticated data access use cases.

+1.

As already stated in the 2.0 discussion, I don't think fetch join has
turned out to be the right approach for controlling pre-fetch.
Therefore I am not in favour of further extending that feature. Rather
invest in a thorough design of fetch plan.

Best regards
Rainer

---
Rainer Schweigkoffer               SAP AG Walldorf
Java Persistence                   TIP Core JI
Core Java Infrastructure           Dietmar-Hopp-Allee 16
Technology & Innovation Platform   D-69190 Walldorf
Building 3, I.3.14                 phone: +49 6227 7 45305
rainer.schweigkoffer_at_sap.com       fax:   +49 6227 7 821177
Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Werner Brandt, Bill 
McDermott (Co-CEO), Gerhard Oswald, Vishal Sikka,
Jim Hagemann Snabe (Co-CEO)
Vorsitzender des Aufsichtsrats/Chairperson of the SAP 
Supervisory 
Board: Hasso Plattner
Registergericht/Commercial Register Mannheim No HRB 350269
Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse 
oder sonstige vertrauliche Informationen enthalten. 
Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist 
Ihnen eine Verwertung des Inhalts, eine Vervielfaeltigung 
oder Weitergabe der E-Mail ausdruecklich untersagt. Bitte 
benachrichtigen Sie uns und vernichten Sie die empfangene 
E-Mail. Vielen Dank.
This e-mail may contain trade secrets or privileged, 
undisclosed, or otherwise confidential information. If you 
have received this e-mail in error, you are hereby 
notified that any review, copying, or distribution of it 
is strictly prohibited. Please inform us immediately and 
destroy the original transmittal. Thank you for your 
cooperation.