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

Re: (ITS#4574) require none doesn't work

> --On Saturday, June 03, 2006 2:48 PM +0000 ando@sys-net.it wrote:
>> I suggest this patch <http://www.sys-net.it/~ando/Download/pierangelo-
>> masarati-2006-06-03-its4574.patch>; I have no means to check if it
>> breaks anything else in back-config.
> Me either... Any suggested ways to proceed on this?

A couple of comments here: we don't need here to allow too much freedom
and generality in configuration.  Note that these comments might apply to
other configuration bits.  Basically we have:

slapd.conf: databases inherit from global; per-databases statements are
additive, except "none" that clears out the value.  So if the intersection
of any database's value with the global value is not equal to the global
value, one needs to clear out the global value first, and then add the
per-database values

back-config: each per-database value needs be added explicitly; if a new
database is created, it inherits from global (FIXME: is this correct?
check) and then it can be modified to reflect additions or modifications.

So we need the "none" capability in slapd.conf to allow elimination of
inheritance, but we don't need it in back-config because we already have
the modify semantics of LDIF (delete, replace and so) whose granularity is
even finer.

Actually, in back-config "none" shouldn't even be allowed, otherwise we'd
need X-ORDERING as well: the result of using "none" depends on when it
occurs with respect to the other values (i.e. a "none" as first value
would be irrelevant, while a "none" as last value would make all the
others irrelevant).

If this discussion is correct, then we could simply handle "none"
specially (and maybe require it to appear as the first value), and leave
the rest as is.


Ing. Pierangelo Masarati
Responsabile Open Solution
OpenLDAP Core Team

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
Office:   +39.02.23998309          
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it