[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: LDAP schema propagation to the backend

To: Mitya Kovalev <mityak@iname.com>
Subject: Re: LDAP schema propagation to the backend
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Date: Fri, 28 Jan 2000 16:05:16 -0800
Cc: jabra@mail.telepac.pt, OpenLDAP Development <openldap-devel@OpenLDAP.org>
In-reply-to: <389222C8.8741C067@iname.com>
References: <3.0.5.32.20000126162044.009886d0@infidel.boolean.net> <3.0.5.32.20000128080238.00985490@infidel.boolean.net>

At 02:14 AM 1/29/00 +0300, Mitya Kovalev wrote:
>Currently I avoid messing with syntax and matching rules by converting filter to
>most relaxed corresponding SQL (that is, CIS matching) to get "candidates", then
>testing them against full filter with test_filter()...

But watch out... CIS may not behave exactly like caseIgnoreMatch.
caseIgnoreMatch does more than just case ignoring (it also ignores
"extra" spaces).  To be able to use the SQL matching, it must
be more relaxed than the LDAP matching rule.

Follow-Ups:
- RE: LDAP schema propagation to the backend
  - From: "Joao Abrantes" <jabra@mail.telepac.pt>

References:
- Re: LDAP schema propagation to the backend
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- RE: LDAP schema propagation to the backend
  - From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Re: LDAP schema propagation to the backend
  - From: Mitya Kovalev <mityak@iname.com>

Prev by Date: Re: LDAP schema propagation to the backend
Next by Date: OpenLDAP on OpenVMS?
Index(es):
- Chronological
- Thread