Changes between Version 1 and Version 2 of Ticket #36438, comment 2
- Timestamp:
- Jun 4, 2025, 11:01:27 AM (3 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36438, comment 2
v1 v2 1 I haven't reproduced myself but given I can't find any logic in `AutoDetector._generate_removed_field` to ensure that `GeneratedField` removals depend on removals of fields they reference this seems legitimate. I suspect field addition suffers from the same problem.1 I haven't reproduced myself but given I can't find any logic in `AutoDetector._generate_removed_field` to ensure that `GeneratedField` removals depend on removals of fields they reference this seems legitimate. I suspect field addition through `makemigrations` suffers from the same problem and that the optimizer can also result in ordering issues because `FieldOperation.references_field` doesn't consider generated field references.