Hi. I could use some help wrapping my mind around what I think is an
incompatibility between sync and the liquibase upgrade scripts.
ConceptReferenceTerm is an OpenmrsObject, meaning that sync is going to pay
attention to it.
However, in the liquibase scripts, the concept_reference_term table is
populated with the following SQL:
INSERT INTO concept_reference_term (concept_reference_term_id,
concept_source_id, code, description, creator, date_created, uuid)
SELECT cm.concept_map_id, cm.source, cm.source_code,
cm.comment, cm.creator, cm.date_created, UUID()
FROM concept_reference_map cm, concept_reference_source crs
WHERE cm.source = crs.concept_source_id
This means that the 'same' ConceptReferenceTerms are going to have
different UUIDs between the parent and child sync servers. So if on the
parent i modify a ConceptReferenceTerm, that's going to cause a sync
failure -- its not going to be able to find the object.
I don't know exactly what ConceptReferenceTerms do -- does it look like
upon upgrading all child servers, we're going to have to override the
liquibase results for this table?
d
_________________________________________
To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to
[email protected] with "SIGNOFF openmrs-devel-l" in the body (not
the subject) of your e-mail.
[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
