Add support for drop_all

[jacobeatsspam]

What it says on the tin. I'm unable to get drop_all to delete views, and I don't see the method mentioned in the documentation, so I'm assuming this needs to be plumbed still.

[DanCardin]

Indeed, this is not plumbed. I'm curious what your usecase is? My only personal reason for create_all is tests, where I've simply never had the need.

I expect it will be very straightfoward to add. basically just register a on before_drop or whatever, and compare_* with a desired metadata state of a MetaData() with nothing registered on it.

[jacobeatsspam]

Yeah, my use case is development workflow on a remote server, where I can't easily trash the entire database instance and start over. I'm also considering whether I want these in alembic at all. Currently, when I register views for alembic, they are re-created for every migration, and it's getting annoying editing every migration to remove redundant ones that haven't changed, but create_all issues a drop-create cycle, which is good enough for even production.

[DanCardin]

erm, why are they changing? i dont really understand lol.

[jacobeatsspam]

lol I'm lost too. The only thing I realized is that two of the views were deleted from the codebase and I forgot, and those are the only two being deleted. I unfortunately have to pause on this issue, but hope to investigate further in a few weeks.

[DanCardin]

Well whether or not you ultimately need it, like i said, it was straightforward to support.

[jacobeatsspam]

Tested locally and can confirm. All views dropped. I'll try to report back when I test with Procedures and Triggers. Thanks again!!