Adding support for cascade drop for tables

In case of complex constrains and migrations, sometimes it's required that table mu be deleted with CASCADE option.
But the best decision of course would be adding a fluent option for drop method: use CASCADE or not?