Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 36144 invoked from network); 1 Feb 2011 13:41:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Feb 2011 13:41:42 -0000 Received: (qmail 56708 invoked by uid 500); 1 Feb 2011 13:41:42 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 56451 invoked by uid 500); 1 Feb 2011 13:41:39 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 56443 invoked by uid 99); 1 Feb 2011 13:41:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 13:41:38 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.18.2.177] (HELO exprod7og112.obsmtp.com) (64.18.2.177) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 01 Feb 2011 13:41:31 +0000 Received: from source ([209.85.161.53]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTUgNdaKze0sAV3ZjdYkgUkoLRMdSgMHm@postini.com; Tue, 01 Feb 2011 05:41:11 PST Received: by fxm11 with SMTP id 11so6957008fxm.12 for ; Tue, 01 Feb 2011 05:41:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.83.134 with SMTP id f6mr4793938fal.1.1296567667668; Tue, 01 Feb 2011 05:41:07 -0800 (PST) Received: by 10.223.78.139 with HTTP; Tue, 1 Feb 2011 05:41:07 -0800 (PST) In-Reply-To: <7BB23DFB-C763-4AD7-B2A4-A85490392322@novlog.com> References: <09057867-617A-4DF2-8C69-A6ED1BD518EB@novlog.com> <7BB23DFB-C763-4AD7-B2A4-A85490392322@novlog.com> Date: Tue, 1 Feb 2011 08:41:07 -0500 Message-ID: Subject: Re: OpenJPA rock and fetch plan is a killing feature. From: Daryl Stultz To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=20cf304345084239d8049b38af86 X-Virus-Checked: Checked by ClamAV on apache.org --20cf304345084239d8049b38af86 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jan 31, 2011 at 5:18 PM, Jean-Baptiste BRIAUD -- Novlog < j-b.briaud@novlog.com> wrote: > http://www.avaje.org/ebean/introquery_join.html > > Fetch path, fetch plan, ... : the same good idea with probably small > implementation differences in different products. > Yes, Ebean does have an analogous feature to Fetch Plan. I was referring to auto-tuning of queries: http://avaje.com/ebean/introquery_autofetch.html So "fetch plan" available when needed but often not needed. I don't think this is a "small implementation difference". -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com http://www.opentempo.com mailto:daryl.stultz@opentempo.com --20cf304345084239d8049b38af86--