Understanding and Deploying LDAP Directory Services > 7. Schema Design > The Schema Checking Process |
The Schema Checking ProcessWhen a new entry is added to the directory or an existing entry is modified, the directory server that processes the request goes through a schema checking process before committing the add or modify request. The schema checking process is done before the directory database itself is altered and ensures that all new or modified directory entries conform to the schema rules. If an entry violates any of the schema rules in effect, the request is rejected by the directory server and a Constraint Violation error is returned to the LDAP client. The steps a server typically performs when checking schema are as follows :
Note that the specifics and order of execution of some of the steps shown may vary in different directory service implementations . However, the basic idea is always the same: the resulting entry (whether new or modified) is checked for complete conformance with the server's schema rules, and an error is sent to the directory client if any problems are found. If there is a schema violation, the entire add or modify operation is rejected by the server. Some implementations, such as the U-M slapd server and the Netscape Directory Server, provide a way to disable schema checking entirely, in which case entries that are added or modified are not checked against the schema rules at all.
|
Index terms contained in this sectioncheckingschemas 2nd 3rd Constraint Violation errors Constraint Violation error schema checking process directories schemas checking process 2nd 3rd 4th schemas checking process 2nd 3rd Constraint Violation errors |
2002, O'Reilly & Associates, Inc. |