Re: Migrations for dropping columns/tables must not have CASCADE keyword

Hi Marcin, I'm sorry to hear that your views got dropped. I hope they were easy to recreate. I imagine the reason the migrations framework uses CASCADE is because we assume Django manages all your database. I know without CASCADE, PostgreSQL (at least) can also be hard to fight against with permi

Migrations for dropping columns/tables must not have CASCADE keyword

Hi. My question is about these two: https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L55 https://github.com/django/django/blob/master/django/db/backends/base/schema.py#L64 Both are loose cannons. All dependent objects are silently destroyed during dropping table or