myway bug dropping non-existent indexes

[srcshelton]

When in a schema script I try to drop an index which doesn't exist the error thrown by mysql is caught by myway and ignored. The rest of the script (and any other script) is run in afterwards. This occurs whether or not other statements were included in the ALTER TABLE. For example the script:

CREATE TABLE `test` (`id` INT UNSIGNED NOT NULL, PRIMARY KEY (`id`));
ALTER TABLE `test`
DROP INDEX `idx_does_not_exist`,
ADD COLUMN `will_not_be_created` INT UNSIGNED NOT NULL;

... produces the following myway console output:

DBD::mysql::db do failed: Can't DROP 'idx_does_not_exist'; check that column/key exists at /usr/local/bin/myway.pl line 2730.

INFO:   Load completed

In this case the column will not be added which could cause unexpected errors in the future.
It would be preferred that myway does not silently hide these errors at all as they imply an assumption made by the developer is not true.

[srcshelton]

Fixed in f0341e1 on branch latest