Nuno Khan

I believe this https://github.com/pinax/pinax-models/pull/11 would fix this behaviour since it uses django admin internal way of getting related models to delete (or not)

@kodeine you can test and see if https://github.com/pinax/pinax-models/pull/11 solves this issue since its already merged

I believe this https://github.com/pinax/pinax-models/pull/11 would fix this behaviour since it uses django admin internal way of getting related models to delete (or not)

@naringas instead of renaming the function why not adding it as a new function to keep backward compatibility?? If i am not mistaken if you rename this you will be...

@naringas exactly.

This should actually be activated by a setting mimiquing the behaviour of the on_delete Cascade and/or Set_Null https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ForeignKey.on_delete Django Default is `Cascade` which is the current behaviour without this PR