Don't forget http://code.djangoproject.com/ticket/7539. The patch is
old--it's for Django 0.96--so it needs to be updated. Hopefully I'll
manage to do this in the next week or two as we start moving our project
from 0.96 to 1.0.x. But it to handles ON CASCADE DELETE / RESTRICT
SET NULL behavio
On 16 feb, 01:28, Karen Tracey wrote:
> On Sun, Feb 15, 2009 at 7:03 PM, Manuel Saelices wrote:
> [snip background]
>
>
>
> > These are the reasons to think in a possible improvement in Django
> > ORM. I've patched django to support a model like this:
>
> > class Master(models.Model):
> > pa
On Sun, Feb 15, 2009 at 7:03 PM, Manuel Saelices wrote:
[snip background]
> These are the reasons to think in a possible improvement in Django
> ORM. I've patched django to support a model like this:
>
> class Master(models.Model):
>pass
>
> class Slave(models.Model):
> master = models.Forei
In one of my Django projects, customer accidentally deleted related
objects because django-batchadmin doesn't advice for related objects
deletion. The question was I thought Django would not delete related
objects in a nullable many to one relation, but Django in fact deleted
it (of course, accord
