You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is if i want to create a new row in concept i need an existing concept_class to reference but if i want to create concept_class i need an existing concept to reference but if i want to create a new concept... you get the point :)
How am i supposed to insert concept data without having some cumbersome scripts that will disable constraints under certain circumstances (which runs against the whole idea of having a data model with constraints in the first place)
I could not find any information on how to solve this in a cleanly manner. if anyone has any hints for me, I would be very grateful. cheers.
The text was updated successfully, but these errors were encountered:
Hi @motey that is a great question. Usually when I load vocabulary, I load it first and then apply the constraints. Especially in postgres it can be very slow to load data into a table that has constraints already applied. @aostropolets , @dimshitc do you guys have any suggestions related to constraints?
Howdy lovely CDM Community,
i am new to all this and i am in the process to create a bunch of python representations for the OMOP-CDM Model (https://github.com/DZD-eV-Diabetes-Research/dzd-omop-cdm-python-models) .
Now i ran into a problem with the CDM schema leaving me scratching my head:
In 5.4 we have the table
concept
which has aNOT NULL
-able foreign key that referencesconcept_class
At the same time we have a
NOT NULL
-able foreign key inconcept_class
that referencesconcept
The problem is if i want to create a new row in
concept
i need an existingconcept_class
to reference but if i want to createconcept_class
i need an existingconcept
to reference but if i want to create a newconcept
... you get the point :)How am i supposed to insert concept data without having some cumbersome scripts that will disable constraints under certain circumstances (which runs against the whole idea of having a data model with constraints in the first place)
I could not find any information on how to solve this in a cleanly manner. if anyone has any hints for me, I would be very grateful. cheers.
The text was updated successfully, but these errors were encountered: