Bug #67899
closedDatabase compare in loop on tx_dam removal after 4.5 > 6.2 migration
100%
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?
Updated by Ingo Müller over 9 years ago
If I ignore the statements of the renaming to zzz_deleted_uid and zzz_deleted_deleted database analyser will just loop in creating and dropping of the key deletedRecords:
Change fields select/deselect all ALTER TABLE tx_dam DROP KEY deletedRecords; ALTER TABLE tx_dam ADD KEY deletedRecords (uid, deleted);
how could i remove those unneeded actions from db analyser?
btw. ubuntu 14.04, php 5.5, mysql 5.5
Updated by Ingo Müller over 9 years ago
- % Done changed from 0 to 100
Deactivating extension dam_falmigration used for migration solved it, as then the unneeded tx_dam table gets dropped in database analyser.
Please close this issue, sorry for bothering.
Updated by Stephan Großberndt over 9 years ago
- Status changed from New to Closed