3 g)2@s\ddlmZddlmZddlmZmZeGdddZGdddeZGd d d Z d S) )total_ordering) ProjectState)CircularDependencyErrorNodeNotFoundErrorc@sXeZdZdZddZddZddZdd Zd d Zd d Z ddZ ddZ ddZ dS)Nodezp A single node in the migration graph. Contains direct links to adjacent nodes in either direction. cCs||_t|_t|_dS)N)keysetchildrenparents)selfrr X/var/www/tester-filtro-web/env/lib/python3.6/site-packages/django/db/migrations/graph.py__init__sz Node.__init__cCs |j|kS)N)r)r otherr r r__eq__sz Node.__eq__cCs |j|kS)N)r)r rr r r__lt__sz Node.__lt__cCs t|jS)N)hashr)r r r r__hash__sz Node.__hash__cCs |j|S)N)r)r itemr r r __getitem__szNode.__getitem__cCs t|jS)N)strr)r r r r__str__sz Node.__str__cCsd|jj|jd|jdfS)Nz<%s: (%r, %r)>rr) __class____name__r)r r r r__repr__"sz Node.__repr__cCs|jj|dS)N)r add)r childr r r add_child%szNode.add_childcCs|jj|dS)N)r r)r parentr r r add_parent(szNode.add_parentN) r __module__ __qualname____doc__rrrrrrrrr r r r rrsrcs(eZdZdZfddZddZZS) DummyNodea A node that doesn't correspond to a migration file on disk. (A squashed migration that was removed, for example.) After the migration graph is processed, all dummy nodes should be removed. If there are any left, a nonexistent dependency error is raised. cstj|||_||_dS)N)superrorigin error_message)r rr&r')rr rr4s zDummyNode.__init__cCst|j|j|jddS)N)r&)rr'rr&)r r r r raise_error9szDummyNode.raise_error)rr!r"r#rr( __classcell__r r )rrr$,s r$c@seZdZdZddZddZddZd+d d Zd d Zd dZ ddZ ddZ ddZ d,ddZ d-ddZd.ddZddZdd Zd!d"Zd#d$Zd%d&Zd/d'd(Zd)d*ZdS)0MigrationGraphaH Represent the digraph of all migrations in a project. Each migration is a node, and each dependency is an edge. There are no implicit dependencies between numbered migrations - the numbering is merely a convention to aid file listing. Every new numbered migration has a declared dependency to the previous number, meaning that VCS branch merges can be detected and resolved. Migrations files can be marked as replacing another set of migrations - this is to support the "squash" feature. The graph handler isn't responsible for these; instead, the code to load them in here should examine the migration files and if the replaced migrations are all either unapplied or not present, it should ignore the replaced ones, load in just the replacing migration, and repoint any dependencies that pointed to the replaced migrations to point to the replacing one. A node should be a tuple: (app_path, migration_name). The tree special-cases things within an app - namely, root nodes and leaf nodes ignore dependencies to other apps. cCsi|_i|_dS)N)node_mapnodes)r r r rrTszMigrationGraph.__init__cCs.||jkstt|}||j|<||j|<dS)N)r+AssertionErrorrr,)r r migrationnoder r radd_nodeXs zMigrationGraph.add_nodecCs$t|||}||j|<d|j|<dS)N)r$r+r,)r rr&r'r/r r radd_dummy_node^s  zMigrationGraph.add_dummy_nodeFcCs||jkr$d||f}|j|||||jkrHd||f}|j||||j|j|j||j|j|j||s|jdS)z This may create dummy nodes if they don't yet exist. If `skip_validation=True`, validate_consistency() should be called afterwards. z=Migration %s dependencies reference nonexistent child node %rz>Migration %s dependencies reference nonexistent parent node %rN)r,r1r+r rvalidate_consistency)r r.rrZskip_validationr'r r radd_dependencycs    zMigrationGraph.add_dependencyc Cst|}y|j|}Wn4tk rJ}ztd|f||WYdd}~XnXx|D]}|jj|d|jj|d}|rRx8|jD].}|jj||j |kr~|j ||j |q~Wx8|jD].}|jj||j |kr|j ||j |qWqRWdS)z Remove each of the `replaced` nodes (when they exist). Any dependencies that were referencing them are changed to reference the `replacement` node instead. zjUnable to find replacement node %r. It was either never added to the migration graph, or has been removed.N) r r+KeyErrorrr,popr r removerrr ) r replacementreplacedreplacement_nodeerrZ replaced_key replaced_noderrr r rremove_replaced_nodeszs.         z$MigrationGraph.remove_replaced_nodesc Cs|jj|dy|jj|}Wn4tk rR}ztd|f||WYdd}~XnXt}t}x0|D](}|jj|}|rf|j|||jO}qfW||8}x<|j D]2} | jj |x |D]}|j | | j |qWqWx|jD]} | j j |qWdS)a* The inverse operation to `remove_replaced_nodes`. Almost. Remove the replacement node `replacement` and remap its child nodes to `replaced` - the list of nodes it would have replaced. Don't remap its parent nodes as they are expected to be correct already. NztUnable to remove replacement node %r. It was either never added to the migration graph, or has been removed already.) r,r5r+r4rr getrr r r6rr ) r r7r8r9r:Zreplaced_nodesZreplaced_nodes_parentsrr;rrr r rremove_replacement_nodes0        z&MigrationGraph.remove_replacement_nodecCsdd|jjDdS)z7Ensure there are no dummy nodes remaining in the graph.cSsg|]}t|tr|jqSr ) isinstancer$r().0nr r r sz7MigrationGraph.validate_consistency..N)r+values)r r r rr2sz#MigrationGraph.validate_consistencycCs*||jkrtd|f||j|j|S)z Given a node, return a list of which previous nodes (dependencies) must be applied, ending with the node itself. This is the list you would follow if applying the migrations to a database. zNode %r not a valid node)r,r iterative_dfsr+)r targetr r r forwards_plans zMigrationGraph.forwards_plancCs.||jkrtd|f||j|j|ddS)z Given a node, return a list of which dependent nodes (dependencies) must be unapplied, ending with the node itself. This is the list you would follow if removing the migrations from a database. zNode %r not a valid nodeF)forwards)r,rrDr+)r rEr r rbackwards_plans zMigrationGraph.backwards_planTcCsg}t}|dfg}xj|r~|j\}}||kr0q|rL|j||j|jq|j|df|ddt|rn|jn|jD7}qW|S)z6Iterative depth-first search for finding dependencies.FTcSsg|] }|dfqS)Fr )r@rAr r rrBsz0MigrationGraph.iterative_dfs..)r r5rappendrsortedr r )r startrGvisitedZ visited_setstackr/ processedr r rrDs   &zMigrationGraph.iterative_dfsNcsXt}xH|jD]>tfdd|jjDr| sB|dkr|jqWt|S)z Return all root nodes - that is, nodes with no dependencies inside their app. These are the starting point for an app. c3s|]}|ddkVqdS)rNr )r@r)r/r r sz,MigrationGraph.root_nodes..r)r r,allr+r rrJ)r approotsr )r/r root_nodess  0zMigrationGraph.root_nodescsXt}xH|jD]>tfdd|jjDr| sB|dkr|jqWt|S)am Return all leaf nodes - that is, nodes with no dependents in their app. These are the "most current" version of an app's schema. Having more than one per app is technically an error, but one that gets handled further up, in the interactive command - it's usually the result of a VCS merge and needs some user input. c3s|]}|ddkVqdS)rNr )r@r)r/r rrOsz,MigrationGraph.leaf_nodes..r)r r,rPr+r rrJ)r rQZleavesr )r/r leaf_nodess  0zMigrationGraph.leaf_nodescCst|j}x|r|j}|g}x|r|d}xr|j|jD]Z}|j}||krv||j|d}tdjdd|D||kr:|j ||j |Pq:W|j}q Wq WdS)Nrz, css|]}d|VqdS)z%s.%sNr )r@rAr r rrOsz3MigrationGraph.ensure_not_cyclic..) r r,r5r+r rindexrjoinrIr6)r todor/rMtoprcycler r rensure_not_cyclics    z MigrationGraph.ensure_not_cycliccCs d|jS)NzGraph: %s nodes, %s edges)_nodes_and_edges)r r r rrszMigrationGraph.__str__cCs|j\}}d|jj||fS)Nz<%s: nodes=%s, edges=%s>)r\rr)r r,edgesr r rrs zMigrationGraph.__repr__cCs"t|jtdd|jjDfS)Ncss|]}t|jVqdS)N)lenr )r@r/r r rrO"sz2MigrationGraph._nodes_and_edges..)r^r,sumr+rC)r r r rr\!szMigrationGraph._nodes_and_edgescCsHg}x>|D]6}x0|j|D]"}||kr|s2||kr|j|qWq W|S)N)rFrI)r r,at_endplanr/r.r r r_generate_plan$s  zMigrationGraph._generate_plancCsn|dkrt|j}|stSt|dts2|g}|j||}t|d}x |D]}|j|j|dd}qNW|S)z Given a migration node or nodes, return a complete ProjectState for it. If at_end is False, return the state before the migration has run. If nodes is not provided, return the overall most current project state. Nr) real_appsF)Zpreserve)listrTrr?tuplerbr,Z mutate_state)r r,r`rcraZ project_stater/r r r make_state,s    zMigrationGraph.make_statecCs ||jkS)N)r,)r r/r r r __contains__>szMigrationGraph.__contains__)F)T)N)N)NTN)rr!r"r#rr0r1r3r<r>r2rFrHrDrSrTr[rrr\rbrfrgr r r rr*=s( #$    r*N) functoolsrZdjango.db.migrations.stater exceptionsrrrr$r*r r r rs  $