Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 26541 invoked from network); 14 Dec 2009 16:01:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Dec 2009 16:01:20 -0000 Received: (qmail 85720 invoked by uid 500); 14 Dec 2009 16:01:20 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 85686 invoked by uid 500); 14 Dec 2009 16:01:20 -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 85676 invoked by uid 99); 14 Dec 2009 16:01:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2009 16:01:20 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=10.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.26] (HELO exprod7og124.obsmtp.com) (64.18.2.26) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 14 Dec 2009 16:01:10 +0000 Received: from source ([209.85.222.197]) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKSyZhMOu7E0X0x6EEQUpk/2rE5rE5D33A@postini.com; Mon, 14 Dec 2009 08:00:50 PST Received: by mail-pz0-f197.google.com with SMTP id 35so2349737pzk.22 for ; Mon, 14 Dec 2009 08:00:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.141.15.10 with SMTP id s10mr3466889rvi.218.1260806448152; Mon, 14 Dec 2009 08:00:48 -0800 (PST) In-Reply-To: <1260804664784-4164748.post@n2.nabble.com> References: <1260416451945-4143547.post@n2.nabble.com> <1260467463538-4146760.post@n2.nabble.com> <1260563468451-4153596.post@n2.nabble.com> <1260570439457-4154130.post@n2.nabble.com> <1260665074872-4158093.post@n2.nabble.com> <1260804664784-4164748.post@n2.nabble.com> Date: Mon, 14 Dec 2009 11:00:48 -0500 Message-ID: Subject: Re: Fetch plan question From: Daryl Stultz To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=000e0cd1153e7902f2047ab26057 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd1153e7902f2047ab26057 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Dec 14, 2009 at 10:31 AM, Pinaki Poddar wrote: > > Hi Daryl, > Prepared Query Cache is used when a JPQL query is executed *more than > once*. Thanks for the explanation. I was under the impression (at least with 1.2.1) that the query cache cannot be enabled unless data cache is enabled. I did not enable data cache (and I'm assuming the default for 2.0 is disabled). The parametrization of the cached SQL is not > always possible -- especially for IN expression parameters which can vary > in > number of parameters on successive executions. I noticed that the queries generated are of the form "where (o.id = 1 or o.id = 2 or o.id = 3)" rather than "where o.id in (1, 2, 3)". Any reason for this? > So, can you please post the test that failed with > openjpa.jdbc.QuerySQLCache=true? > Also mention which version of OpenJPA was used for the test. > My current production code is 1.2.1 based. I have to pull things apart a bit to run it with 2.0M3. I'm too busy right now, but I'll try to squeeze it in sometime over the next couple of weeks. -- Daryl Stultz _____________________________________ 6 Degrees Software and Consulting, Inc. http://www.6degrees.com mailto:daryl@6degrees.com --000e0cd1153e7902f2047ab26057--