Changes between Version 1 and Version 2 of Ticket #34151, comment 28
- Timestamp:
- Apr 24, 2026, 5:43:19 AM (3 weeks ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34151, comment 28
v1 v2 1 1 Hi Jacob, let me clarify. The result in comment:22 is not by applying the changes in comment:20, but rather by applying the changes in the original report and in comment:6. (comment:20 was only my alternative attempt to reproduce the issue when I didn't know which database was used). 2 2 3 That is, the issue before django 6.0 was when changing both field type AND name in one single step, which will result in a database in an inconsistent state regarding the foreign keys.3 That is, the issue before django 6.0 was when changing both field type AND name in one single step, which generates a script to recreate the column, which, when applying, will result in a database in an inconsistent state regarding the foreign keys. 4 4 5 5 After django 6.0 the migration script is the same, but the execution will fail, which will at least leave the database in a consistent state.