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

Re: Invalid DN after schema change

To: Michael Ströder <michael@stroeder.com>
Subject: Re: Invalid DN after schema change
From: Howard Chu <hyc@symas.com>
Date: Fri, 29 May 2009 02:01:19 -0700
Cc: openldap-devel@openldap.org
In-reply-to: <4A1FA09B.9010601@stroeder.com>
References: <4A1FA09B.9010601@stroeder.com>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; rv:1.9.1b5pre) Gecko/20090517 SeaMonkey/2.0a1pre Firefox/3.0.3

Michael Ströder wrote:

HI!

If one plays around with schema and an attribute type used in the RDN
of an entry is no longer present then this entry is no longer readable
because whenever a request is sent to slapd invalidDNSyntax is returned.
This leads to the situation that a client can't even explicitly delete
this offending entry anymore.

I'd vote for relaxing the schema-based DN checking in case of search,
rename (only old DN), modify and delete requests a bit so that after a
schema change the data can be corrected with normal client tools without
server down-time.

Any thoughts on this?


"Don't do that."

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/

Follow-Ups:
- Re: Invalid DN after schema change
  - From: Michael Ströder <michael@stroeder.com>

References:
- Invalid DN after schema change
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: Invalid DN after schema change
Next by Date: Re: Invalid DN after schema change
Index(es):
- Chronological
- Thread