Opened 8 years ago

Closed 8 years ago

#25988 closed Cleanup/optimization (wontfix)

Change django.db.models.deletion.CASCADE to django.db.models.deletion.PROTECT while creating migrations

Reported by: Saurabh Agrawal Owned by: nobody
Component: Migrations Version: 1.9
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

By default, on deletion, the changes shouldn't be cascaded, but protected. Results in loss of data if the migrations generated are not checked carefully.

Change History (1)

comment:1 by Tim Graham, 8 years ago

Resolution: → wontfix
Status: new → closed

Thanks for the suggestion, but it's obsolete because Django 1.9 ​deprecates the default value for on_delete so that in Django 2.0, the developer must specify a value.

Note: See TracTickets for help on using tickets.
Back to Top