Administration Guide › Set Up Schemas › Object Classes and Object Class Identifiers › Object Class Storage › Pruning and Replacing Object Classes

Pruning and Replacing Object Classes

It is more space-efficient to configure the DSA to prune all inherited object classes except the lowest (inetOrgPerson) when creating the entry, and to replace all the superior object classes (organizationalPerson, Person, and top) when returning the entry as a result of a client search.

The following boolean configuration settings control the pruning and replacing of object classes:

set prune-oc-parents

Removes redundant superior object classes when new entries are created.

set return-oc-parents

Replaces the superior object classes to entries returned to the client.

set add-oc-parents

Causes parent object classes to be added when entries are added. For example, consider adding a Democorp entry with the following class:

• inetOrgPerson

This control adds all the parent classes. As a result the entry holds the following classes:

• top
• person
• organizationalPerson
• inetOrgPerson

When prune-oc-parents or return-oc-parents is set, searching entries using an object class filter (for example, oc=Person) does not return any entries, because the specified object class of Person is not present in the data; it is added only to search results that contain the inetOrgPerson object class.