Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 13943 invoked from network); 11 Dec 2009 21:55:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Dec 2009 21:55:29 -0000 Received: (qmail 91557 invoked by uid 500); 11 Dec 2009 21:55:28 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 91472 invoked by uid 500); 11 Dec 2009 21:55:28 -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 91462 invoked by uid 99); 11 Dec 2009 21:55:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2009 21:55:28 +0000 X-ASF-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.18.2.28] (HELO exprod7og125.obsmtp.com) (64.18.2.28) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 11 Dec 2009 21:55:24 +0000 Received: from source ([209.85.222.199]) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKSyK/tlQVx4rnN7OY1GJ7JO8EmKR7QbX9@postini.com; Fri, 11 Dec 2009 13:55:04 PST Received: by pzk37 with SMTP id 37so902726pzk.10 for ; Fri, 11 Dec 2009 13:55:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.82.42 with SMTP id f42mr1186391rvb.52.1260568502352; Fri, 11 Dec 2009 13:55:02 -0800 (PST) In-Reply-To: <1260563468451-4153596.post@n2.nabble.com> References: <12D996978341E849B21C51CC97F4771D01FAA44E@mail3.oams.com> <5FAE6D4B-6F14-46A0-899A-9EEF271154AF@novlog.com> <014E3069-732E-438C-972F-723E836A8388@SUN.com> <1260416451945-4143547.post@n2.nabble.com> <1260467463538-4146760.post@n2.nabble.com> <1260563468451-4153596.post@n2.nabble.com> Date: Fri, 11 Dec 2009 16:55:02 -0500 Message-ID: Subject: Re: Fetch plan question From: Daryl Stultz To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=000e0cd1549ecc3cd1047a7af904 --000e0cd1549ecc3cd1047a7af904 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Dec 11, 2009 at 3:31 PM, Pinaki Poddar wrote: > > Hi Daryl, > The change is committed on trunk at revision 889799. > Can you try to see if it resolves the problem? > > I got the latest as of this afternoon, a few past 889799. I've tested against my isolated unit test and it's good. I'll try it in my full application when I get a chance. I've pulled back from using fetch plan completely until this is resolved. Can you give me some idea of the problem, perhaps I can use fetch plan selectively knowing what the arrangement is that yields the error? Thanks for the quick attention! -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:daryl@6degrees.com --000e0cd1549ecc3cd1047a7af904--