Add options to disable re-installation/merging/comparison of existing platform ontologies during platform startup
Currently we store the graph.tg
file contents of all ontologies installed in the database by the default platform installation logic in SimanticsPlatform
.
They are store in the database by DatabaseManagement
. The actual TG file data is only needed when merging changes to existing ontologies into a started workspace.
In many products it is not useful to actually have ontology merging available at all for any built-in ontologies, which means the ontology merging procedure could receive an efficiency boost in two ways:
- Getting rid of extra work related to analysing whether changes need to merged for your ontologies
- The comparison is currently based on pre-calculated and cached hashes so not much work is saved by this
- Getting rid of storing the completely immutable basic ontologies in the database as
.tg
files.- These files can take up several tens of megabytes depending on your product and the plug-ins you're using.
So, what we essentially want is:
-
a mechanism to disable storage of .tg
files for ontologies in the database to reduce the size of the database and baselined workspaces. -
the mechanism should be disabled in development mode (running from IDE) but testable from that environment as well