custom sql irreversible on dropall


i create a couple of custom enum types using sql tags as part of a changeset.  I want to be able to drop those types on dropAll.  I tried a rollback tag but I suspect this is only executed for rollback situations where something has gone wrong with an update.  the types still existed after a dropall at least.

what should i do to run some custom sql as part of the dropall procedure?


I’ve downloaded the source for the plugin and core and can see that it’s not possible to run custom sql for the dropall.  should i add this as an idea?  i can potentially contribute the feature myself though i’m totally new to this community so would like to know what your thoughts are around this?