As a reference this was originally posted in [#2006]
I'm not sure to understand why you would like to remove the key constraints in the DB ? Can you give some more details ?
Also, documentating the db schema can be dangerous due to the very true nature of iTop : it is a customizable product, the metamodel can vary with every new module added to the product, and these modifications are of course reflected directly to the db schema...
But as iTop does the XML/PHP compilation to create its datamodel and then update the DB, it provides all of the methods to understand the overall structure of the datamodel.
In my opinion a lead would be to have an endpoint giving all of the datamodel structure using those methods (look at the MetaModel class in particular)
But as I didn't get what was your need exactly, I'm not sure of the best way ?
Hello,
As a reference this was originally posted in [#2006]
I'm not sure to understand why you would like to remove the key constraints in the DB ? Can you give some more details ?
Also, documentating the db schema can be dangerous due to the very true nature of iTop : it is a customizable product, the metamodel can vary with every new module added to the product, and these modifications are of course reflected directly to the db schema...
But as iTop does the XML/PHP compilation to create its datamodel and then update the DB, it provides all of the methods to understand the overall structure of the datamodel.
In my opinion a lead would be to have an endpoint giving all of the datamodel structure using those methods (look at the MetaModel class in particular)
But as I didn't get what was your need exactly, I'm not sure of the best way ?
Related
Tickets:
#2006