Hi Alex!
I didn't want to propel you to do things, that are scheduled for later
implementation. But schema validation would definitly be my number one
wish (and probably the number one of many end users wishlists ...). So I
would appreciate schema checks.
I will add appropriate tests to the test suite (some are already in
place, one of them raised this defect).
Question for the central strategy / overall solution / architecture ...:
Have you planned to allow the administrator to disable the validation
during maintenance times, e.g. for a faster bul load?
Some servers allows this and have different strategies for
implementation ...
Alex Karasulu (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DIREVE-230?page=comments#action_12319753 ]
Alex Karasulu commented on DIREVE-230:
--------------------------------------
I think this is all a result of not having proper schema checking in place. If
the server checked to make sure a modify operation left a valid structural
objectClass in place after all mods are applied then we would not have this
problem. Likewise we should not allow the deletion of the RDN attributes
without an RDN change. Overall schema checking is a mess we really need a
central strategy behind it. For now I will add schema checks to make sure
these consistency issues do not arrise.
