4-day-mbse-with-core9_2018-reva

CORE Database Merge Operations • Full import of a database to a non-empty image • The two files are merged subject to the following rules: • For any imported element that has the same name and element class as an element in the database, then: • Any defined attributes in the input file replace those in database; • If an imported relation has targets, then those relationships replace those in the database; • If an element is found that the import application cannot recognize, then an error message is generated and placed in the conflict file and the import continues (indicates the name exists but a create_element action does not exist for the named element); • If a create_element action in the input file corresponds to an existing element in the database, then an error report is placed in the conflict file and the import continues. • Any structure defined in the input file replaces the corresponding structure in the database or creates a new structure if one did not previously exist.

477

CORE Database Merge Operations

• Incremental import of a database to a non-empty image • The design files are merged subject to the following rules : • For any imported element that has the same name and element class as an element in the database, then: • Any defined attributes in the input file replace those in database; • Any imported relationship in the input having targets results in those changes being made to the database (additions and removal of targets); • If an element is found which does not exist in the database (create_element does not exist in the input file), then a conflict is noted but the element is not added to the database; • If a create_element name has the same name as an existing name in the database, then the element is created with a name suffix of “$n” where n starts at one and is incremented for each duplicate. A conflict file entry is produced (this accommodates the case where two or more individuals create elements, in the same class, with the same name. • Any structure defined in the input file replaces the corresponding structure in the database or creates a new structure if one did not previously exist.

478