carry forward force_policy to the Queryset (#74)

* carry forward force_policy to the Queryset force_policy feature is currently only available on the model instances. Enable this feature for SafeDeleteQuerySet as well. * Carry forward force_policy to the Queryset force_policy feature is currently only available on the model instances. Enable this feature for SafeDeleteQuerySet as well. * Update CHANGES
makinacorpus · Apr 4, 2017 · 8173705 · 8173705
1 parent 139a027
commit 8173705
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/CHANGES b/CHANGES
@@ -9,6 +9,7 @@ CHANGELOG
 
 - Filtering on the deleted field is done on evaluation.
 - Added specific managers: all_objects and deleted_objects.
+- Added 'force_policy' feature to SafeDeleteQuerySet.
 
 ** Removed **
 

diff --git a/safedelete/queryset.py b/safedelete/queryset.py
@@ -14,7 +14,7 @@ class SafeDeleteQueryset(query.QuerySet):
     QuerySet itself is evaluated.
     """
 
-    def delete(self):
+    def delete(self, force_policy=None):
         """Overrides bulk delete behaviour.
 
         .. note::
@@ -27,7 +27,7 @@ def delete(self):
         assert self.query.can_filter(), "Cannot use 'limit' or 'offset' with delete."
         # TODO: Replace this by bulk update if we can
         for obj in self.all():
-            obj.delete()
+            obj.delete(force_policy=force_policy)
         self._result_cache = None
     delete.alters_data = True