pinax-models icon indicating copy to clipboard operation
pinax-models copied to clipboard

Provide Support for Logical Deletes on Models and in the Django Admin

Results 13 pinax-models issues
Sort by recently updated
recently updated
newest added

Looking for maintainers! There is a lot of pull requests and open issues that the current maintainers, myself included, are just not finding the time to properly get to. Maybe...

question

These fields are redundant for logical deletion. Model itself named ``LogicalDeleteModel`` and seeing this fields inside it are surprising. Also, there are a few apps that provide similarly functionality: *...

Patch is missing for this repo

Based on feedback from detox, I removed tests/urls.py and reference in runtests.py due to absence of urls. * Add Django 2.0 compatibility testing * Drop Django 1.8, 1.9, 1.10, and...

A recent commit by @paltman removed from .admin import LogicalDeleteModelAdmin # noqa from .models import LogicalDeleteModel # noqa from the __init__.py file in pinax/models. I'm not sure why it was...

docs
For Discussion

As referenced in #13, not all related objects should be deleted. But I think that ``ForeignKey`` should resolve it by itself, using ``on_delete`` param. The same applies to ``OneToOneField``. But...

The "current" version of pinax-models (e.g. what you get when you use `pip install pinax-models`) appears to date back to a much earlier version of the code. As such, it...

enhancement

If you have two models that inherit from the logicaldelete Model one with a GenericForeignKey pointing to the other and the other with a GenericRelation for the type of the...

enhancement

When an object is "deleted", its related models which the foreign key to this object is `null=True` should not be deleted. Instead the related model foreign key should be set...

enhancement