Michael Ströder wrote:
Upgraded what? slapd? Was there a change in BDB format from 2.4.29 to
My question was about the state of the assertion and whether the
interpretation (and as a consequence the slapcat/slapadd-operation)
Howard says schema change can be one reason. Always slapcat/slapadd
when tweaking existing schema elements. In this case if one version
of the attribute got a normaliser and the other did not.
Of course the various standards say existing schemas should never
change, but keeping them frozen is sometimes easier said than done.
I mentioned upgrade because incompatible changes sometimes slip
through, typically in a bugfix where the code doesn't stay backwards
bug-compatible. So I always slapcat/slapadd when upgrading too,
just in case.