Changes between Initial Version and Version 1 of Ticket #31255, comment 27
- Timestamp:
- Sep 7, 2026, 6:24:22 PM (6 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31255, comment 27
initial v1 1 1 The proposed changes ignore the problem mentioned in comment:13 and captured by the `test_non_cyclical_models_removals` regression test. 2 2 3 To drop two tables that have a referential cycle one of the two must be altered to drop its foreign key constraint first on in Django model terms, a `RemoveField` **must** be present and this `RemoveField` and `DeleteModel` for the same model cannot be systematically reduced.3 To drop two tables that have a referential cycle one of the two must be altered to drop its foreign key constraint first. Django model terms this means that a `RemoveField` **must** be present and that `RemoveField` and `DeleteModel` for the same model cannot be systematically reduced like proposed by the submitted patch.