3 ªôÁg³ ã@sGdd„dƒZdS)c@s eZdZdZdd„Zdd„ZdS)ÚMigrationOptimizera] Power the optimization process, where you provide a list of Operations and you are returned a list of equal or shorter length - operations are merged into one if possible. For example, a CreateModel and an AddField can be optimized into a new CreateModel, and CreateModel and DeleteModel can be optimized into nothing. cCsJ|dkrtdƒ‚d|_x.|j||ƒ}|jd7_||kr>|S|}qWdS)a… Main optimization entry point. Pass in a list of Operation instances, get out a new list of Operation instances. Unfortunately, due to the scope of the optimization (two combinable operations might be separated by several hundred others), this can't be done as a peephole optimization with checks/output implemented on the Operations themselves; instead, the optimizer looks at each individual operation and scans forwards in the list to see if there are any matches, stopping at boundaries - operations which can't be optimized over (RunSQL, operations on the same field/model, etc.) The inner loop is run until the starting list is the same as the result list, and then the result is returned. This means that operation optimization must be stable and always return an equal or shorter list. Nzapp_label must be a str.éé)Ú TypeErrorZ _iterationsÚoptimize_inner)ÚselfÚ operationsÚ app_labelÚresult©r ú\/var/www/tester-filtro-web/env/lib/python3.6/site-packages/django/db/migrations/optimizer.pyÚoptimize s zMigrationOptimizer.optimizec sög}xìt|ƒD]à\}}d}xÒt||dd…ƒD]°\}‰|jˆˆƒ}t|tƒrØ||d||d…} |r€|j| ƒ|j|ƒn:t‡‡fdd„| Dƒƒr®|j|ƒ|j| ƒn |j|ƒP|j|||dd…ƒ|S|s0d}q0W|j|ƒqW|S)zInner optimization loop.TrNc3s|]}|jˆˆƒdkVqdS)TN)Úreduce)Ú.0Úop)rÚotherr r ú 5sz4MigrationOptimizer.optimize_inner..éF)Ú enumerater Ú isinstanceÚlistÚextendÚallÚappend) rrrZnew_operationsÚiZ operationÚrightÚjr Z in_betweenr )rrr r(s*       z!MigrationOptimizer.optimize_innerN)Ú__name__Ú __module__Ú __qualname__Ú__doc__r rr r r r rs rN)rr r r r Ús