You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2019/06/25 23:00:05 UTC
[jira] [Updated] (DIRSERVER-888) Add a verification before deleting
an Object Class in the schema
[ https://issues.apache.org/jira/browse/DIRSERVER-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-888:
----------------------------------------
Component/s: ldap
> Add a verification before deleting an Object Class in the schema
> ----------------------------------------------------------------
>
> Key: DIRSERVER-888
> URL: https://issues.apache.org/jira/browse/DIRSERVER-888
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: ldap
> Affects Versions: 1.5.0
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Alex Karasulu
> Priority: Major
> Fix For: 2.1.0
>
>
> While I was playing a little with the new dynamic schema in ADS 1.5, I found an interesting situation.
> Here's the scenario:
> I created a new AT called 'MyAT' and a new OC called 'MyOC' which has 'MyAT' in its May list.
> After a refresh of the Connection in LDAP Studio, I was able to create a new entry using 'MyOC' as OC. This entry was 'MyAT=test, dc=example, dc=com'.
> Then I was wondering how would react the server if I delete 'MyAT' from the schema.
> I got a warning telling me that an entity was depending on it (it was 'MyOC' of course).
> Very Great! :)
> Then I tried to delete 'MyOC'... and then... no warning...
> I could delete it successfully.
> After that, I was also able to delete 'MyAT', since there was no more dependency on it.
> That left my server with a pretty strange situation : having an entry depending on OC and AT that doesn't exists anymore in the schema...
> While trying to load children of 'dc=example, dc=com', I got an error : "Error while reading entry
> [LDAP: error code 33 - failed on search operation: OID for name 'myoc' was not found within the OID registry]"
> I think it would be a good idea, before deleting an OC in the schema, to verify if there's not one (or more) entry depending on that OC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org