Issue Bug Closed

#67899Database compare in loop on tx_dam removal after 4.5 > 6.2 migration

Ingo Müller 07/03/15, 09:46 updated 07/06/15, 13:17

Description

I migrated from 4.5.40 to 6.2.11 with DAM migration going all smooth (thanks fot that).
Also all database compare actions to remove all my outdated extension tables went well (first to zzz_deleted_, then to real drop) only the tx_dam table gives me headaches.

Database analyser seems to be in a loop so that the table tx_dam can never be fully dropped.
And if i drop that table manually (there isn’t anything useful in there anymore), database compare recreates the table with wrong columns:

CREATE TABLE tx_dam ( _missingfile tinyint(4) unsigned NOT NULL default '0', KEY deletedRecords (uid, deleted), KEY missingFiles (_missingfile) );    

Database update failed
Error: Key column 'uid' doesn't exist in table

If i create it manually again with those missing columns,

CREATE TABLE tx_dam ( _missingfile tinyint(4) unsigned NOT NULL default '0', uid tinyint(4), deleted tinyint (4), KEY deletedRecords (uid, deleted), KEY missingFiles (_missingfile) );

database analyzer starts it’s dropping routine again but fails as the drop key / add key lines won’t work:

    select/deselect all
    ALTER TABLE tx_dam DROP KEY deletedRecords;
    ALTER TABLE tx_dam ADD KEY deletedRecords (uid, deleted);

Remove unused fields (rename with prefix)

    select/deselect all
    ALTER TABLE tx_dam CHANGE uid zzz_deleted_uid int(11) NOT NULL default NULL;
    ALTER TABLE tx_dam CHANGE deleted zzz_deleted_deleted int(11) NOT NULL default NULL;
Database analyzer
Add fields to tables

    select/deselect all
    ALTER TABLE tx_dam ADD KEY deletedRecords (uid, deleted);

Database update failed
Error: Key column 'uid' doesn't exist in table

And then i could recreate those columns again, but well it will get in this loop again.
Anybody?

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.