XF@sdZddlmZddlmZddlmZddlmZm Z m Z ddl m Z ddl mZdd d d gZGd dde ZGd d d e ZGdd d e ZGdd d e ZdS)zR Query subclasses which provide extra functionality beyond simple data retrieval. ) FieldError) connections)Q)CURSORGET_ITERATOR_CHUNK_SIZE NO_RESULTS)Query)six DeleteQuery UpdateQuery InsertQueryAggregateQueryc@sCeZdZdZdZddZdddZdd ZdS) r zo Delete queries are done through this class, since they are more constrained than general queries. ZSQLDeleteCompilercCs>|g|_||_|j|jt}|r:|jSdS)Nr)tableswhere get_compiler execute_sqlrrowcount)selftablerusingcursorrM/home/ubuntu/projects/ifolica/build/django/django/db/models/sql/subqueries.pydo_querys  zDeleteQuery.do_queryNcCsd}|s|jj}nxtdt|tD]l}|j|_|jti|||t|j d6||j |jj |jd|7}q7W|S)z Set up and execute delete queries for all the objects in pk_list. More than one physical query may be executed if there are a lot of values in pk_list. rZ__inr) get_metapkrangelenr where_classradd_qrZattnamerZdb_table)rpk_listrfieldZ num_deletedoffsetrrr delete_batchs &,zDeleteQuery.delete_batchcs+|jj|jfddjD}| sO||jkr^j|_n|jjj}t|jj st |j ddd}|sdS|j ||Sj |j|jg_}|j|_|jtd||j|jt}|r'|jSdS)z Delete the queryset in one SQL query (if possible). For simple queries this is done by copying the query.query.where to self.query, for complex queries by using subquery. cs#g|]}j|r|qSr)Zalias_refcount).0t)innerqrr <s z)DeleteQuery.delete_qs..rZflatTrpk__in)queryZget_initial_aliasrrmodel_metarrfeaturesZupdate_can_self_selectlistZ values_listr#Zclear_select_clauseZget_colselectrrrrrrr)rr)rZinnerq_used_tablesrvaluesrr)r&r delete_qs1s&    zDeleteQuery.delete_qs)__name__ __module__ __qualname____doc__compilerrr#r0rrrrr s  cseZdZdZdZfddZddZdfdd Zd d Zd d Z ddZ ddZ ddZ S)r z+ Represents an "update" SQL query. ZSQLUpdateCompilercs'tt|j|||jdS)N)superr __init__ _setup_query)rargskwargs) __class__rrr7\szUpdateQuery.__init__cCs1g|_d|_t|ds-i|_ndS)z Runs on initialization and after cloning. Any attributes that would normally be set in __init__ should go in here, instead, so that they are also set up after a clone() call. Nrelated_updates)r/ related_idshasattrr<)rrrrr8`s  zUpdateQuery._setup_queryNc s(tt|j|d|jj|S)Nr<)r6r cloner<copy)rklassr:)r;rrr?kszUpdateQuery.clonecCs}|j|xitdt|tD]O}|j|_|jtd|||t|j|j t q&WdS)Nrr() add_update_valuesrrrrrrrrrr)rr r/rr"rrr update_batchns  $zUpdateQuery.update_batchcCsg}xtj|D]\}}|jj|}|joG|j pR|j }|jjj}| s}|j r|j rt d|n||jjk r|j |||qn|j |||fqW|j|S)z Convert a dictionary of field name to value mappings into an update query. This is the entry point for the public update() method on querysets. zMCannot update model field %r (only non-relations and foreign keys permitted).)r iteritemsr get_fieldZ auto_createdZconcreter*r+Zconcrete_modelZ is_relationZ many_to_manyradd_related_updateappendadd_update_fields)rr/ values_seqnamevalr!directr*rrrrBus zUpdateQuery.add_update_valuescCs|jj|dS)z Append a sequence of (field, model, value) triples to the internal list that will be used to generate the UPDATE query. Might be more usefully called add_update_targets() to hint at the extra information here. N)r/extend)rrIrrrrHszUpdateQuery.add_update_fieldscCs)|jj|gj|d|fdS)z Adds (name, value) to an update query for an ancestor model. Updates are coalesced so that we only run one update query per ancestor. N)r< setdefaultrG)rr*r!valuerrrrFszUpdateQuery.add_related_updatecCs|js gSg}xjtj|jD]V\}}t|}||_|jdk ro|jd|jfn|j|q&W|S)z Returns a list of query objects: one for each update required to an ancestor model. Each query will have the same filtering conditions as the current query but will only update a single table. Nr()r<r rDr r/r=Z add_filterrG)rresultr*r/r)rrrget_related_updatess   zUpdateQuery.get_related_updates) r1r2r3r4r5r7r8r?rCrBrHrFrQrr)r;rr Us      csLeZdZdZfddZdfddZddd ZS) r ZSQLInsertCompilercs/tt|j||g|_g|_dS)N)r6r r7fieldsobjs)rr9r:)r;rrr7s zInsertQuery.__init__Nc s^i|jddd6|jddd6|jd6}|j|tt|j||S)NrRrSraw)rRrSrTupdater6r r?)rrAr:extras)r;rrr?s   zInsertQuery.cloneFcCs||_||_||_dS)a Set up the insert query from the 'insert_values' dictionary. The dictionary gives the model field names and their target values. If 'raw_values' is True, the values in the 'insert_values' dictionary are inserted directly into the query, rather than passed as SQL parameters. This provides a way to insert NULL and DEFAULT keywords into the query, for example. N)rRrSrT)rrRrSrTrrr insert_valuess  zInsertQuery.insert_values)r1r2r3r5r7r?rWrr)r;rr s  c@s(eZdZdZdZddZdS)r z An AggregateQuery takes another query as a parameter to the FROM clause and only selects the elements in the provided list. ZSQLAggregateCompilercCs1|j|jdddd\|_|_dS)NZwith_col_aliasesTsubquery)rZas_sqlrXZ sub_params)rr)rrrr add_subqueryszAggregateQuery.add_subqueryN)r1r2r3r4r5rYrrrrr s N)r4Zdjango.core.exceptionsrZ django.dbrZdjango.db.models.query_utilsrZdjango.db.models.sql.constantsrrrZdjango.db.models.sql.queryrZ django.utilsr __all__r r r r rrrrsDX