When restoring a database backup it happens to appear that the constraints are not set (mostly under Windows), because of an error during the restore process. This can cause an inconsistency in the database, when deleting anything in GECAMed.
To restore the constraints in the database you can use this SQL-file, which contains all constraints of the GECAMed version 1.2.00.
You can create an SQL-file containing the constraints for your GECAMed version by doing the following:
When inserting the backup there might occur some error:
In that case you either have not extracted the related set-search-path statement or it wasn't executed before. You can either add it before the alter-statement (it looks like this: “SET search_path = «schema», pg_catalog;”) or directly add the schema before the table (it looks like this: “ALTER TABLE ONLY «schema».«table name» ADD CONSTRAINT …” - if the table name occurs once more in the statement you need to add the schema there as well).
This constraint already exists. You can skip this statement.
This constraint already exists, You can skip this statement.
There is already an inconsistency in your database. You need to correct this first, before you can add this constraint.