>>This feels more like a problem to be solved at the database level; the >>ideal solution would be to set 'ON DELETE SET NULL' for the >>foreign-key column (assuming -- and I don't know if this is the case >>-- that Django is doing 'ON DELETE CASCADE'). Just make sure that >>column will accept NULL as a value. > > > But that's moot because apparently Django doesn't output that in the SQL. > > http://code.djangoproject.com/ticket/2288 <-- for those who want to > follow its progress.
Ok, good to know that the issue is an issue. In the meantime, I figured I'd hack around it by making a custom delete method for the admin interface that first changes foreign keys to nulls and then deletes the page. I definitely want the client having to delete two things seperately instead of being able to accidentally kill a page. Any idea where in the docs/code I'd start looking for how to do this? I'm okay with writing SQL myself. Thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
