Changes between Version 2 and Version 3 of Ticket #34151, comment 28


Ignore:
Timestamp:
Apr 24, 2026, 6:08:06 AM (3 weeks ago)
Author:
Carol Naranjo

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #34151, comment 28

    v2 v3  
    33That 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.
    44
    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.
     5After django 6.0 the migration script is the same, but the execution will fail, which will at least leave the Postgres database in a consistent state. I didn't bisect the exact commit, but from the release notes I would assume it relates to: [https://docs.djangoproject.com/en/6.0/releases/6.0/#database-backend-api] --> "BaseDatabaseSchemaEditor and PostgreSQL backends no longer use CASCADE when dropping a column."
Back to Top