Neither did I until today. It is understandable that from a use-case perspective, inlines look less like 'Deletes' and more like 'Disassociates' (from the admin model). Janet thought so in the office when she nuked a few years worth of survey data, and I think its a rather blameless mistake. Nevermind that, we already agree the cascading delete warning is a good thing.
Apparently the form-checkbox nature of the delete button makes form- save and cascade delete warn very tricky. Filed a ticket: http://code.djangoproject.com/ticket/14411 A far less tricky situation would be to turn the delete from a form element into a button and give the usual cascading delete warning. carljm pointed out at the ticket discussion that this is "an alternative that's just as bad". I can hardly agree that a potentially cleared form (but probably not, with modern browsers), is anywhere near equal to an accidentally cleansed table. One seems orders worse, but perspectives vary I guess. And if that's really a horror we can't bear, there's always a javascript warning. Got squashed prematurely IMHO. There several better ways we could treat these situations and prompt for cascading deletes. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
