While this error message is useful when performing most operations. There are times when someone might want to add an auto_increment primary ID column to a table that doesn't currently have one. Since the trigger would not have a identifier to key a DELETE off of this message is displayed.
It would be nice to allow these types of operations:
pt-online-schema-change --alter "ADD COLUMN _id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY" u=user,p='pass',D=mydatabase,t=mytable --no-drop-new-table --no-swap-tables --no-check-alter --dry-run
Then it would be up to the user to rename and drop tables manually. Thoughts?
While this error message is useful when performing most operations. There are times when someone might want to add an auto_increment primary ID column to a table that doesn't currently have one. Since the trigger would not have a identifier to key a DELETE off of this message is displayed.
It would be nice to allow these types of operations:
pt-online- schema- change --alter "ADD COLUMN _id INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY" u=user, p='pass' ,D=mydatabase, t=mytable --no-drop-new-table --no-swap-tables --no-check-alter --dry-run
Then it would be up to the user to rename and drop tables manually. Thoughts?