Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 69379 invoked from network); 21 May 2007 12:08:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 May 2007 12:08:59 -0000 Received: (qmail 47310 invoked by uid 500); 21 May 2007 12:09:04 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 47099 invoked by uid 500); 21 May 2007 12:09:04 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 47088 invoked by uid 99); 21 May 2007 12:09:04 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 05:09:04 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [81.169.146.160] (HELO mo-p00-ob.rzone.de) (81.169.146.160) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 May 2007 05:08:56 -0700 Received: from [127.0.0.1] ([145.253.187.146]) by post.webmailer.de (mrclete mo40) (RZmta 6.5) with ESMTP id A0433bj4LAJS1F for ; Mon, 21 May 2007 14:08:34 +0200 (MEST) Message-ID: <46518BC4.6010007@labeo.de> Date: Mon, 21 May 2007 14:08:36 +0200 From: Stefan Zoerner User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: DIRSERVER-936 & 927 Questions References: <465180ED.3070009@labeo.de> <46518853.4080104@labeo.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RZG-AUTH: kR2YrGeU3i5GJZNxbYfAbITnBeX/YWiFZ/RSZNrjTu1WUdpHVnruOkDtj54= X-RZG-CLASS-ID: mo00 X-Virus-Checked: Checked by ClamAV on apache.org Emmanuel Lecharny wrote: > - Compare should be accepted whatever the AT is Isn't it necessary to determine a matching rule for a compare operation? How do we accomplish this without an attribute type? If the attribute type is not in the schema any longer, a compare should raise an error, I think. Sorry for making the problem even more complicated :-(