Comment 7 for bug 933232

I was able to reproduce this by add SET SQL_LOG_BIN=0 to the sql file for alter_active_table.t. At present, the test file loads the table to be altered on the master which replicates to the slave. Therefore, the changes made by the triggers don't cause an error because the slave also has the table.

After talking with Baron, and in view of the fact that we plan to redesign this tool in the future, for the current version (2.0.x), we are going to add an --execute option that the user must specify before the tool will actually work. This is to encourage users to read the docs, which we'll also update to mention that altering a table on a master that doesn't exist on a slave will cause a problem, other issues with replication, etc.