On Tue, 2009-03-31 at 14:48 -0500, Jeremy Dunck wrote: > Malcolm, Jacob pointed me at you, since the code in question was a > commit around QSRF-time. > > I'm aware of ticket #7539, but would prefer to keep the scope narrower > and ask the hopefully-useful question-- is #9308 a bug? If so, I'd > like to close it for 1.1. > > In summary, #9308 describes a situation where B has a nullable FK to > A, and an instance of A is being deleted. Currently, any B's related > to A also get deleted.
I was mostly trying to retain whatever the previous behaviour was with delete in qsrf. I disagree with Django's cascading delete behaviour, but wasn't interested in changing it at the time, since I was mostly bug-fixing, no apple-cart-upsetting. In the case of #9308, specifically, I think setting the related pointers to NULL would be a better solution, but I'm not sure if it's considered a fundamental change in behaviour, inconsistent with what we're doing now. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
