Re: Incosistent config after schema modification

[Quanah Gibson-Mount <quanah@symas.com>]

--On Wednesday, January 10, 2018 9:46 PM +0100 Ervin Hegedüs 
<airween@gmail.com> wrote:

> Hi,
>
> On Wed, Jan 10, 2018 at 12:17:47PM -0800, Quanah Gibson-Mount wrote:
> > --On Wednesday, January 10, 2018 9:11 PM +0100 Ervin Hegedüs
> > <airween@gmail.com> wrote:
> >
> > > is there any relevant difference between the replace and
> > > delete/add methods, which triggered this state in the DB?
> >
> > Jon already answered that.  When you use replace, it replaces *all*
> > values with what you supply in the operation.
>
> but he wrote the answer for MULTI-VALUE's attribute, but I'm
> useing SINGLE-VALUE - or em I missing?

This is clearly multiple values for the "olcAttributeTypes" attribute:

dn: cn={5}cppm,cn=schema,cn=config
changetype: modify
replace: olcAttributeTypes
olcAttributeTypes: {0}( cppmAttrs:1 NAME 'cppmCreateTime' DESC 'Create time'
 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{20} SINGLE-VALUE )
olcAttributeTypes: {5}( cppmAttrs:6 NAME 'cppmExpireTime' DESC 'Expire time'
 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{20} SINGLE-VALUE )
olcAttributeTypes: {7}( cppmAttrs:8 NAME 'cppmActivationTime' DESC 'Activati
on time' SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{20} SINGLE-VALUE )

You supplied 3 values for it with a replace operation.  Which means *only* 
those 3 values now exist for that object.

--Quanah



--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>