Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C1B8776AF for ; Fri, 5 Aug 2011 14:31:27 +0000 (UTC) Received: (qmail 42998 invoked by uid 500); 5 Aug 2011 14:31:27 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 42957 invoked by uid 500); 5 Aug 2011 14:31:26 -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 42947 invoked by uid 99); 5 Aug 2011 14:31:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2011 14:31:26 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michael.d.dick@gmail.com designates 209.85.160.174 as permitted sender) Received: from [209.85.160.174] (HELO mail-gy0-f174.google.com) (209.85.160.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Aug 2011 14:31:20 +0000 Received: by gya6 with SMTP id 6so227977gya.33 for ; Fri, 05 Aug 2011 07:30:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=bHkcZ2RerZVhm8zS7q5RuDENWOWVX+2DBF31rhNahdQ=; b=jKWSTVWp2OAeJVOyaKCpRs+Snj3R4NXWPuyapi6x64sDR5j6hYgzAcbB2cAi31k7fj 23exB2W0EpvP93GTU5EUP9B1i92fSS1lI/yQ10dkl4a/PwJEf5pyJeTi5PqtyHhzKa2t jPjLofU9xIKd5iR8eW4uVOiaZLOYE9rcgVIQ0= Received: by 10.101.28.22 with SMTP id f22mr561269anj.155.1312554659082; Fri, 05 Aug 2011 07:30:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.240.18 with HTTP; Fri, 5 Aug 2011 07:30:39 -0700 (PDT) In-Reply-To: <1312550844832-6656525.post@n2.nabble.com> References: <1312297119532-6645128.post@n2.nabble.com> <1312385001457-6649130.post@n2.nabble.com> <1312465424494-6652752.post@n2.nabble.com> <1312469294977-6653036.post@n2.nabble.com> <1312550844832-6656525.post@n2.nabble.com> From: Michael Dick Date: Fri, 5 Aug 2011 09:30:39 -0500 Message-ID: Subject: Re: Version of all children is incremented in OneToMany when merging parent entity To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=001636b2b0ac33f14404a9c2f2bc X-Virus-Checked: Checked by ClamAV on apache.org --001636b2b0ac33f14404a9c2f2bc Content-Type: text/plain; charset=ISO-8859-1 Statement batching is an OpenJPA optimization. By default OpenJPA will try to use JDBC statement batching. There's a section in the user manual at : http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_dbsetup_stmtbatch. Depending on the application, statement batching can provide a significant performance boost. For example inserting several rows to the same table can be batched, and executed in a single conversation with the database. If your application updates several different tables, or different parts of the same table, statement batching provides less of a benefit. If you believe it will not benefit your app, or you want to remove the batching from the equation, you can disable batching by adding the following property to persistence.xml : Hope this helps, -mike On Fri, Aug 5, 2011 at 8:27 AM, M. Walter wrote: > Please can anyone explain to me when "batching prepstmnt" occurs? What > exactly is the cause of this? What are the reasons causing OpenJPA to batch > statements? > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Version-of-all-children-is-incremented-in-OneToMany-when-merging-parent-entity-tp6645128p6656525.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > --001636b2b0ac33f14404a9c2f2bc--