Howard Chu writes:
Hallvard B Furuseth wrote:
> Is the problem only to (make it feasible to) detect this situation, or
> also to act on it? To detect it, I assume Delete before returning
> notAllowedOnNonLeaf could search with scope onelevel/children, and see
> if it finds any entires.
Yes... back-bdb would also need to check this for modrdn as well. Seems
like quite a lot of extra expense to perform this check each time.
Only at failure. Maybe it's more work than I imagine - it's an index
after all. But IIRC we already have similar slowdowns in situations I'd
assume are more common. When deleting multiple attribute values in an
entry have the same hash, or something.