Re: Custom default managers interfere with delete operations

[Ned Batchelder]

Done: http://code.djangoproject.com/ticket/2698 --Ned. Russell Keith-Magee wrote: On 9/10/06, Ned Batchelder <[EMAIL PROTECTED]> wrote: No filtering allowed. Hrm. I think you might be right. Taking a closer look, it seems that the deletion algorithm is fairly conservative; I can't see a way of constructing a non-default related manager that would exclude an object from deletion without breaking referential integrity. Lodge an ticket; try your hand at a patch if you're feeling adventurous. -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---