Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

The upgrades from 4.1.0, 4.1.1, 4.1.2 and 4.1.3 to 4.50 have database inconsistencies #12

Open
jpingo opened this Issue May 31, 2011 · 1 comment

Comments

Projects
None yet
2 participants

jpingo commented May 31, 2011

There are some database inconsistencies when doing the following upgrades

4.1.0 -> 4.5.0
To synchronize your database with the distribution setup, run the following SQL commands:
ALTER TABLE ezinfocollection ADD INDEX ezinfocollection_co_id_created ( contentobject_id, created );
ALTER TABLE ezkeyword_attribute_link ADD INDEX ezkeyword_attr_link_oaid ( objectattribute_id );
ALTER TABLE ezworkflow_event CHANGE COLUMN data_text1 data_text1 varchar(255) DEFAULT NULL;
ALTER TABLE ezworkflow_event CHANGE COLUMN data_text2 data_text2 varchar(255) DEFAULT NULL;
ALTER TABLE ezworkflow_event CHANGE COLUMN data_text3 data_text3 varchar(255) DEFAULT NULL;
ALTER TABLE ezworkflow_event CHANGE COLUMN data_text4 data_text4 varchar(255) DEFAULT NULL;

4.1.1, 4.1.2, 4.1.3 -> 4.5.0
To synchronize your database with the distribution setup, run the following SQL commands:
ALTER TABLE ezinfocollection ADD INDEX ezinfocollection_co_id_created ( contentobject_id, created );
ALTER TABLE ezkeyword_attribute_link ADD INDEX ezkeyword_attr_link_oaid ( objectattribute_id );

Maybe this is related to the dbupdate-4.1.0-to-4.2.0.sql file that need's manual changes before applying.
This upgrades were made using and ezflow installation

These DB inconsistencies appear when you run the admin's DB consistency checks before upgrading, right? So it is not directly related to a bug in ezupgrade but to oddities in eZ Publish sql files?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment