Changes between Version 2 and Version 3 of Ticket #36199


Ignore:
Timestamp:
Feb 18, 2025, 4:38:33 PM (3 days ago)
Author:
Ian Bicket
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #36199 – Description

    v2 v3  
    1010
    1111'''Description:'''
    12 When running makemigrations on a Django 5.1 project using a PostgreSQL backend, the migration autodetector redundantly generates a migration that removes and then recreates a Coalesce index where the output_field is set to TextField(). This occurs because the autodetector incorrectly registers the TextField in the existing and new application state as distinct, leading to continuous migration creation even when no schema changes have occurred.
     12When running makemigrations on a Django 5.1 project using a PostgreSQL backend, the migration autodetector redundantly generates a migration that removes and then recreates a GinIndex with a SearchVector over a Coalesced field where the output_field parameter is set to TextField(). Furthermore, makemigrations can be run an arbitrary number of times, each execution re-creating what is essentially the same migration, removing and recreating the index.
    1313
    1414'''Steps to Reproduce:'''
Back to Top