Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 26197 invoked from network); 20 Aug 2007 23:48:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Aug 2007 23:48:21 -0000 Received: (qmail 88177 invoked by uid 500); 20 Aug 2007 23:48:18 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 88140 invoked by uid 500); 20 Aug 2007 23:48:18 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 88131 invoked by uid 99); 20 Aug 2007 23:48:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2007 16:48:18 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of plinskey@gmail.com designates 64.233.166.178 as permitted sender) Received: from [64.233.166.178] (HELO py-out-1112.google.com) (64.233.166.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2007 23:48:15 +0000 Received: by py-out-1112.google.com with SMTP id f31so2227699pyh for ; Mon, 20 Aug 2007 16:47:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ucKkkl6GDuDmqImYKdM9U2jeTYP/4fjwLtrZ5XO5VdUil1t5yjRDLczUkCHyYzc44P7p+62Ehxmq5x2XWgcJKYl/MKi0xKFs9EBcGP4S5VoTSgVntWJ7AHpUrvRrDGnU9k9MEtoCnzDreFR6GXb8yTywBHyJdM6O9NVpE+fkHRU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nYlKrvoJg4SKCpLgq88jxnyhVpu8MBUPHn6KXAsnPx0ONrEESHCbJStdbwNmwsi2YcAJxmoUk+kFtkf8RzBvhzlY4sML32NfhM+QAM5bdTzxfEHGW6rTx+U1etNYfyrGVV4CMbiiHRa+KBalhT33gFkslWxWtKMz7k7xSSTb1Zc= Received: by 10.35.117.5 with SMTP id u5mr8001548pym.1187653673954; Mon, 20 Aug 2007 16:47:53 -0700 (PDT) Received: by 10.35.8.4 with HTTP; Mon, 20 Aug 2007 16:47:53 -0700 (PDT) Message-ID: <7262f25e0708201647hceafa68n14c8e8450eb21e8a@mail.gmail.com> Date: Mon, 20 Aug 2007 16:47:53 -0700 From: "Patrick Linskey" To: dev@openjpa.apache.org Subject: Re: XML datatypes and data caching In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7262f25e0708201231rc10bb9bge1ba9053c15f5665@mail.gmail.com> <7262f25e0708201545i4c407792h94f53f7154093f9b@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Do we make a copy of the data in the cache? I.e., if you load some data so it gets into cache, then change something inside the XML graph, but do not commit, are the changes visible? -Patrick On 8/20/07, catalina wei wrote: > Patrick, > Right now the persistent field mapped to XML column is cached just like > other persist field when DataCache is turned on. > > Do we want to change this behavior to not caching the xml field value? > I don't understand why we want to prevent the xml field from getting into > cache. > > The same testcase in openjpa-persistence-jdbc ran OK with DataCache turned > on. > > Catalina > > On 8/20/07, Patrick Linskey wrote: > > > > Great. If you could add a test case, that would be very helpful for > > ongoing verification. > > > > I think that initially, it is probably sufficient to just prevent > > these field types from getting into cache. > > > > -Patrick > > > > On 8/20/07, catalina wei wrote: > > > Hi Patrick, > > > I can verify this. I will post result shortly. > > > > > > Catalina > > > On 8/20/07, Patrick Linskey wrote: > > > > > > > > Hi, > > > > > > > > Have we done any testing of the interaction between XML datatypes and > > > > the data cache? > > > > > > > > -Patrick > > > > > > > > -- > > > > Patrick Linskey > > > > 202 669 5907 > > > > > > > > > > > > > -- > > Patrick Linskey > > 202 669 5907 > > > -- Patrick Linskey 202 669 5907