Using cross schema inheritance results in weird behaviour

[willemijn-oudijk]

Have you checked if this issue already exists?

• yes

Molgenis EMX2 version

Software version: 13.171.0. Database version: 33.

Description

For ERDERA we have a schema for staging areas, this includes a table that uses cross schema inheritance, i.e., the table inherits from a table from another schema. This seems to work as expected. However, within the staging area, the schema editor does not work. Additionally, when you download the schema of the staging area, the refschema column is empty.

Reproduction steps

1. Go to 'https://emx2.dev.molgenis.org'
2. Create a new schema with the PATIENT_REGISTRY profile and name it erdera.
3. Create a new schema with the PATIENT_REGISTRY_ID_BANK schema and name it Staging area ids.
4. Create a new schema with the PATIENT_REGISTRY_STAGING profile and name it Staging area UMCG. (This schema is dependent on the first two, therefore they need to be created). Within this schema, there is a table called Materials, this table inherits from Sample identifiers in the schema Staging area ids (cross schema inheritance).
5. Go to the schema editor in Staging area UMCG - see that you cannot see the schema, even though you can see the table overview.
6. Additionally in Staging area UMCG, export the schema and see that refSchema is empty in the Materials definition.

Expected behaviour

I expected the schema editor to work as expected and the refSchema to display Staging area ids as it does here.

System configuration

• Device:
• Operating system:
• Browser: