2iAddlmZddlmZmZmZmZmZddlm Z ddl m Z ddl m Z mZddl mZedd ZGd d e j"Zy ) )Counter)DictOptionalTupleTypeTypeVar)models)query) HARD_DELETE NO_DELETE)SafeDeleteQuery_QSSafeDeleteQueryset)boundc deZdZdZ ddeeejdeedee dee e ejfffd Z e dZ de _dd eed eee e efffd Zde_d eee e effffd Zdd eed eee e efffd Zde_dded effd ZfdZxZS)ra7Default queryset for the SafeDeleteManager. Takes care of "lazily evaluating" safedelete QuerySets. QuerySets passed within the ``SafeDeleteQueryset`` will have all of the models available. The deleted policy is evaluated at the very end of the chain when the QuerySet itself is evaluated. modelr usinghintscptt| |||||xst|j|_y)N)rr rr)superr__init__rrr )selfrr rr __class__s J/var/www/html/acx/venv/lib/python3.12/site-packages/safedelete/queryset.pyrzSafeDeleteQueryset.__init__s5  $0uEQV^c0d&+&Jtzz/J cLddlm}|j|}d|_|S)zNOverride as_manager behavior to ensure we create a SafeDeleteManager. r )SafeDeleteManagerT)managersr from_queryset_built_with_as_manager)clsrmanagers r as_managerzSafeDeleteQueryset.as_manager s* 06#11#68)-&rT force_policyreturncp|jjsJd|tk(rdifS|tk(r|j St }|j D](}|j|\}}|j|*d|_ t|jt|fS)a1Overrides bulk delete behaviour. .. note:: The current implementation loses performance on bulk deletes in order to safely delete objects according to the deletion policies set. .. seealso:: :py:func:`safedelete.models.SafeDeleteModel.delete` z+Cannot use 'limit' or 'offset' with delete.rr%N) r can_filterr r hard_delete_policy_actionralldeleteupdate _result_cachesumvaluesdict)rr%deleted_counterobj_delete_responses rr,zSafeDeleteQueryset.delete,szz$$&U(UU& 9 $r7N [ (113 3'.yOxxz 8%(ZZ\Z%J"?&&7 8"&D --/0$2GG GrcT|jjt| SN)r _filter_visibilityrr,)rrs rr*z,SafeDeleteQueryset.hard_delete_policy_actionFs  %%'w~rc$|jjsJdt}|jD](}|j |\}}|j |*d|_t|jt|fS)aUndelete all soft deleted models. .. note:: The current implementation loses performance on bulk undeletes in order to call the pre/post-save signals. .. seealso:: :py:func:`safedelete.models.SafeDeleteModel.undelete` z-Cannot use 'limit' or 'offset' with undelete.r(N) r r)rr+undeleter-r.r/r0r1)rr%undeleted_counterr3r4undelete_responses rr:zSafeDeleteQueryset.undeleteKszz$$&W(WW&%,Y88: 8C#&<<\<#J A  $ $%6 7 8"$++-.5F0GGGrrcN|||j_tt|S)aOverride so related managers can also see the deleted models. A model's m2m field does not easily have access to `all_objects` and so setting `force_visibility` to True is a way of getting all of the models. It is not recommended to use `force_visibility` outside of related models because it will create a new queryset. Args: force_visibility: Force a deletion visibility. (default: {None}) )r _safedelete_force_visibilityrrr+)rforce_visibilityrs rr+zSafeDeleteQueryset.all_s(  '6FDJJ 3'244rc|j}|jjdi|tt||i|S)N)_cloner check_field_filterrrfilter)rargskwargsquerysetrs rrDzSafeDeleteQueryset.filterns=;;=)))3F3'94J6JJr)NNNNr7)__name__ __module__ __qualname____doc__rrr Modelrstrrr classmethodr$ queryset_onlyintrr, alters_datar*r:rr+rD __classcell__)rs@rrr s937/3#'7; KD./KO,KC= K Dfll!234 K $JH8C=HE#tCQTH~BUXH$ H 5# 5 5KKrN) collectionsrtypingrrrrr django.dbr django.db.modelsr configr r rrQuerySetrrArrrYs;77"*" e/0eKeKr