From dev-return-19049-apmail-jackrabbit-dev-archive=jackrabbit.apache.org@jackrabbit.apache.org Mon Jun 02 08:23:00 2008 Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 45407 invoked from network); 2 Jun 2008 08:22:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jun 2008 08:22:59 -0000 Received: (qmail 14586 invoked by uid 500); 2 Jun 2008 08:23:01 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 14540 invoked by uid 500); 2 Jun 2008 08:23:01 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 14523 invoked by uid 99); 2 Jun 2008 08:23:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 01:23:01 -0700 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.8.61.8] (HELO spamslammer2.tirol.gv.at) (194.8.61.8) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2008 08:22:07 +0000 Received: from mailscan1.tirol.local (unknown [10.10.128.204]) by spamslammer2.tirol.gv.at (Spamslammer) with ESMTP id 4FC421210A05A6FF for ; Mon, 2 Jun 2008 10:22:30 +0200 (CEST) Received: from mxs0.tirol.local (unverified) by mailscan1.tirol.local (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Mon, 2 Jun 2008 10:22:30 +0200 Received: from mxs01.tirol.local ([10.10.128.211]) by mxs0.tirol.local with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Jun 2008 10:22:30 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: Another DataStore Question ... Date: Mon, 2 Jun 2008 10:22:32 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Another DataStore Question ... Thread-Index: AcjCIreoSpPdJ2jNQO++lgiS9qV4swCZphlw References: From: =?iso-8859-1?Q?K=D6LL_Claus?= To: X-OriginalArrivalTime: 02 Jun 2008 08:22:30.0441 (UTC) FILETIME=[CCBAB190:01C8C489] X-Virus-Checked: Checked by ClamAV on apache.org i have tested it and if you enable the datastore on a existing workspace the update operation will write the binary into the datastore but leaves the old binary in the blobstore i think the old binary should be deleted in the blobstore because if you read the node the old binary will also=20 be loaded but no more be needed. WDOT ? claus -----Urspr=FCngliche Nachricht----- Von: K=D6LL Claus [mailto:C.KOELL@TIROL.GV.AT]=20 Gesendet: Freitag, 30. Mai 2008 09:00 An: dev@jackrabbit.apache.org Betreff: Another DataStore Question ... if i have a already running workspace with a BundlePersistenceManager = (oracle) configured . If i now enable the datastore, what happens to files that will be = updated ? will the binaries be deleted in the bundle and now stored in the = datastore or will the binaries be kept in the bundle ? thanks claus