Changes between Initial Version and Version 1 of Ticket #26292, comment 1
- Timestamp:
- Mar 6, 2016, 5:47:45 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26292, comment 1
initial v1 1 1 While working on this, I started toying around with the idea of building the migration graph in a more complex way where it's aware of applied/non-applied and replacing/non-replacing migrations. Something along the lines of a directional graph with coloured nodes (denoting applied/non-applied) and coloured edges (denoting dependency/replaces). 2 2 3 This would still spawn dummy nodes as it builds the graph, but once finished, an extra function could then be run over the graph - something like `simplify` or `resolve` - where the graph would resolve all the replacing migrations internally , simplifying itself back down to the form it has currently.3 This would still spawn dummy nodes as it builds the graph, but once finished, an extra function could then be run over the graph - something like `simplify` or `resolve` - where the graph would resolve all the replacing migrations internally along with validating that no dummy migrations remain, simplifying itself back down to the form it has currently. 4 4 5 5 It's not the path I'm taking currently, as I'm trying to avoid giving the graph too much knowledge of stuff that's only needed for its initialisation. Seems to belong more to the loader. But just thought I'd leave this idea here as food for thought.