Hi Quanah, thanks,
On Wed, Jan 10, 2018 at 10:24:22AM -0800, Quanah Gibson-Mount wrote: > --On Wednesday, January 10, 2018 6:16 PM +0000 Jon C Kidder [...] > As a side note, you can delete specific values by using their weight, as > well. For example: > > dn: <whatever> > changetype: modify > delete: olcAttributeTypes > olcAttributeTypes: {7} > > Would delete the 8th attribute (since the weights are zero based) > > You can also use the weight to insert a value, like: > > dn: <whatever> > changetype: modify > add: olcAttributeTypes > 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 ) > > would insert cppmAttrs as the 8th value, and anything from what was the 8th > value and up would be renumbered accordingly. is there any relevant difference between the replace and delete/add methods, which triggered this state in the DB? What's the solution to avoid this? Thanks, a.