Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 49470 invoked from network); 20 Jul 2007 08:41:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jul 2007 08:41:45 -0000 Received: (qmail 1867 invoked by uid 500); 20 Jul 2007 08:41:11 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 1850 invoked by uid 500); 20 Jul 2007 08:41:11 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 1841 invoked by uid 99); 20 Jul 2007 08:41:11 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 01:41:11 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com designates 209.85.132.249 as permitted sender) Received: from [209.85.132.249] (HELO an-out-0708.google.com) (209.85.132.249) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 01:41:09 -0700 Received: by an-out-0708.google.com with SMTP id c37so195258anc for ; Fri, 20 Jul 2007 01:40:48 -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=CAdhAY7ms50cUEaFfu6dZMt4IBOBQz5IWX67fcNyPvKD/iVrWwCndqMhtwWt9b4HEvNdKDsGdm0GxS/67jqje6tJ6FW/gBSphMhq7g1valBxNFsJvAhcoaD0f+9s1bfwQxSiRYmJT9RRM4MoBuxd2DpgW0LqLiXIS5Pu/lPc/Ww= 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=FzaRhDafneY1RVVdBmBxDkMUNWcbw5hnw2AZWfeBe0EvCmTum6v23O6cPbXfZlJOrTc7iedslxSWaMmeqDLWXyVE/XGZjQYSrX/64h6Sk/9aCrlDqUAOVuObIztzYe25BBl/e5ehaJ5+4viXnNttC6qodXgIEMrUltzjQ/qzR4Y= Received: by 10.100.165.9 with SMTP id n9mr121290ane.1184920848454; Fri, 20 Jul 2007 01:40:48 -0700 (PDT) Received: by 10.100.163.1 with HTTP; Fri, 20 Jul 2007 01:40:48 -0700 (PDT) Message-ID: <510143ac0707200140g4d2ac26chbf8df75e8ab085eb@mail.gmail.com> Date: Fri, 20 Jul 2007 11:40:48 +0300 From: "Jukka Zitting" To: users@jackrabbit.apache.org Subject: Re: Isolation level inconsistency. In-Reply-To: <46A07239.2060901@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070719233057.7B70810FB051@herse.apache.org> <46A06850.4050303@gmx.de> <46A07239.2060901@gmx.de> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 7/20/07, Julian Reschke wrote: > Alexandru Popescu ? wrote: > > I would really appreciate if somebody would post on this thread a > > scenario in which the current behavior is proving helpful (and I have > > in mind the scenario posted here: searching for a John and getting a > > Joe instead -- frankly speaking I would be totally surprised in real > > life if I would be looking for my wife and getting somebody else > > instead :-) ). > > I don't think the current JCR behavior was specced this way because > there are uses cases needing it. It's simply a result of queries working > against the persisted state (as the workspace methods), while the > regular read messages don't. Also, I still don't think there are real use cases for the opposite requirement, i.e. having transient changes visible in search. The real world analogue would be that you are getting married and even though you've already said "I do", the magistrate would still claim that you are not married until the proper paperwork has been submitted. :-) BR, Jukka Zitting