On Wed, Dec 10, 2008 at 3:04 PM, David Cramer <[EMAIL PROTECTED]> wrote: > > To be perfectly honest, I'm +1 on a solution. I didn't realize this > was happening either. > > Time to monkey-patch QuerySet's delete() method :) > > (I'm also a bit curious as to how its handling cascades in MySQL when > it's not looping through each object)
I'd like to make sure I understand what we're talking about here. model_instance.delete() nulls any instances with nullable FKs to the deleted instance, right? The problem AFAICS, is that QuerySet.delete is not so careful, and deletes all FK records, even if they are nullable? And was it always so, or was this introduced in QuerySet-refactor, or at some other time? I don't see a mention on BackwardsIncompatibleChanges and friends. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
