[data: dbscripts/xml/upgrade/3.2.0_versioning.xml] ERROR: Upgrade failed: DB: ERROR: null value in column “setting_type” violates not-null constraint DETALHE: Failing row contains (47515, , country, , null).
…is similar to the one you posted above, but this time for the
author_settings table instead of
journal_settings. It is again caused by ADODB not dropping a constraint. It can be resolved by executing this query before running the upgrade script:
ALTER TABLE author_settings ALTER COLUMN setting_type DROP NOT NULL;
For this error:
[data: dbscripts/xml/upgrade/3.2.0_update.xml] ERROR: Upgrade failed: DB: ERROR: null value in column “email_id” violates not-null constraint DETALHE: Failing row contains (null, pt_BR, subject, Avaliação da edição de texto concluída).
…this looks like a data error. You either appear to have entries in
email_templates without an
email_id being set (this should be impossible due to constraints), or you have entries in
email_templates that don’t have corresponding entries in
email_templates_data by the conditions in the above query. If you haven’t customized those templates, the best solution is probably to remove the rows that correspond with the error from
Public Knowledge Project Team