On Thu, Dec 1, 2011 at 11:26 PM, Yo-Yo Ma <baxterstock...@gmail.com> wrote: > My proposal is to add a new on_delete=models.SET-ish feature (or a new > kwarg altogether) which would, when specified, cause the parent > object's delete to loop through an iterator of the related instances > and call the delete method on each for me.
Hello Yo-Yo Ma, I don't quite understand the use-case for this. So if the model is this... class Table(models.Model): restaurant = models.ForeignKey(Restaurant, on_delete=models.CALL_DELETE) Wouldn't that suggest that deleting the table would delete the underlying restaurant? That seems backwards -- cascading deletion works the *other* way (e.g., if you delete a restaurant, then any Table with a ForeignKey to it would get deleted). Sorry if I'm being dense and am missing something. Adrian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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.
