#35487: Removal of CASCADE in DROP COLUMN migration operation
-----------------------------------------+------------------------
Reporter: Petr Přikryl | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 5.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Created based on discussion in https://forum.djangoproject.com/t
/removefield-dropping-views-without-notice/31409
Arguments:
* Consistency acrocss backends. Cascade is used for postgres backend only.
* Cascade is no more needed as constraints and sequences are dropped
explicitly. Next, sequences are being replaced by new identity columns.
* No side effects - unexpected removals in DB schema.
* Test suite is passing after cascade removal.
--
Ticket URL: <https://code.djangoproject.com/ticket/35487>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018fc39b8ef5-717460f9-b8c1-4b8e-8d13-6878a15418db-000000%40eu-central-1.amazonses.com.
