I went through the api and attempted a delete of the Cat Option Combos for the Cat Combo and was returned an error saying the deletion couldn’t proceed because of an association with the dataelementoperand table.
So, I have several rows in dataelementoperand table preventing me from deleting several catoptioncombos. Now, these rows seems to be orphans, because they have no children in the following tables: datadimensionitem, datasetoperands, sectiongreyedfields.
Is that correct? Should I delete these manually via SQL?
could you please try to delete these dataelementoperands with SQL and see if you get any complaints from PostgreSQL constraints?
If not they are orphans - we need to look for places where these are not cleaned up. If you get complaints, please let us know from which constraints/tables.
I went through the api and attempted a delete of the Cat Option Combos for the Cat Combo and was returned an error saying the deletion couldn’t proceed because of an association with the dataelementoperand table.
So, I have several rows in dataelementoperand table preventing me from deleting several catoptioncombos. Now, these rows seems to be orphans, because they have no children in the following tables: datadimensionitem, datasetoperands, sectiongreyedfields.
Is that correct? Should I delete these manually via SQL?
I went through the api and attempted a delete of the Cat Option Combos for the Cat Combo and was returned an error saying the deletion couldn’t proceed because of an association with the dataelementoperand table.
So, I have several rows in dataelementoperand table preventing me from deleting several catoptioncombos. Now, these rows seems to be orphans, because they have no children in the following tables: datadimensionitem, datasetoperands, sectiongreyedfields.
<Screen Shot 2016-06-09 at 9.38.25 AM.png>
Is that correct? Should I delete these manually via SQL?
Skype: blake.a.hansen | 2900 K Street, Suite 404, Washington D.C. 20007
On 9 Jun 2016, at 18:48, Lars Helge Øverland lars@dhis2.org wrote:
Hi Blake,
could you please try to delete these dataelementoperands with SQL and see if you get any complaints from PostgreSQL constraints?
If not they are orphans - we need to look for places where these are not cleaned up. If you get complaints, please let us know from which constraints/tables.
I went through the api and attempted a delete of the Cat Option Combos for the Cat Combo and was returned an error saying the deletion couldn’t proceed because of an association with the dataelementoperand table.
So, I have several rows in dataelementoperand table preventing me from deleting several catoptioncombos. Now, these rows seems to be orphans, because they have no children in the following tables: datadimensionitem, datasetoperands, sectiongreyedfields.
<Screen Shot 2016-06-09 at 9.38.25 AM.png>
Is that correct? Should I delete these manually via SQL?