Comments on: A Django Model Manager for Soft Deleting Records and How to Customize the Django Admin

By: Nitin Nain

Nitin Nain — Tue, 12 May 2020 19:23:12 +0000

There's so much great content like this that you don't get to because of Google's search algorithm! Instead all that you see on Google are posts on Medium by some college chump trying to plug their biodata :/

By: How can I easily mark records as deleted in Django models instead of actually deleting them? – Loitools.com

Sun, 16 Feb 2020 23:33:05 +0000

[...] A Django Model Manager for Soft Deleting Records and How to Customize the Django Admin [...]

By: the martian

the martian — Mon, 30 Mar 2015 03:18:01 +0000

the martian…

A Django Model Manager for Soft Deleting Records and How to Customize the Django Admin | Code Spatter…

By: simply click the following web site

simply click the following web site — Fri, 16 May 2014 02:44:16 +0000

simply click the following web site…

A Django Model Manager for Soft Deleting Records and How to Customize the Django Admin | Code Spatter…

By: black

black — Tue, 30 Nov 2010 15:16:21 +0000

Hello, Your thoughts is very helpful for us . Thanks

By: black

black — Tue, 30 Nov 2010 09:16:21 +0000

Hello, Your thoughts is very helpful for us . Thanks

By: Guetux

Guetux — Sun, 28 Nov 2010 00:24:43 +0000

Thank you, this helped me a lot!

BTW, with django 1.2 and the new multi db support, unfortunatley this doesn't work anymore, as the save_base method prunes the deleted objects with by calling the using(foo) method on the manager. To make this on still work, SoftDeleteManager needs to define something like this:

def using(self, *args, **kwargs):
''' Needed to support multi db infrastructure since django 1.2'''
return self.all_with_deleted().using(*args, **kwargs)

Unfortunatley this removes the possibility of this "hack" to work with multiple dbs...

Anyway, it still helped me a lot, thanks again!

By: Greg Allard

Greg Allard — Mon, 10 Aug 2009 14:11:07 +0000

That would work. If you are using a signal (pre_delete or post_delete), you might need to send it from the new function since you wouldn't want to call the real delete.

I've been doing object.deleted = 1 object.save() and not calling or overriding delete(). That way I still have the option to do the real delete in case I need it. You could probably make a real_delete() function to do that if needed though.

By: Dave

Dave — Mon, 10 Aug 2009 11:17:49 +0000

I think I must be missing something, as I cant see where you're setting the flag “deleted”.

Would overriding the models delete function, setting delete=True and saving suffice?

By: Greg Allard

Greg Allard — Wed, 22 Jul 2009 19:37:32 +0000

I tested this out with a simple many to many example and I am not getting the soft deleted objects returned. With objects = SoftDeleteManager the many to many queries will be using get_query_set() which won't return the soft deleted records. I might need to see an example of how you are getting the deleted results to be able to figure out what is going on. I tried it with some_object.related_things.all() and the returned set won't have deleted related_things.