Changes between Version 1 and Version 2 of Ticket #33483


Ignore:
Timestamp:
Feb 1, 2022, 9:04:21 AM (3 years ago)
Author:
Marti Raudsepp
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33483 – Description

    v1 v2  
    1 I have been using the `django-celery-results` project with Django on an Oracle database. We had issues upgrading to 2.1+ versions. (One of those issues was fixed in django-celery-results 2.2.0, the other issue remained: https://github.com/celery/django-celery-results/issues/222)
     1I have been using the `django-celery-results` project with Django on an Oracle database. I had issues upgrading to 2.1+ versions. (One of those issues was fixed in django-celery-results 2.2.0, the other issue remained: https://github.com/celery/django-celery-results/issues/222)
    22
    33Whenever running `makemigrations` with the newer version, it would attempt to create a new migration file to drop all indexes and recreate them with a different name. This happens because 2.1.0 introduced some `AddIndex` migrations.
    … …  
    2424=== Reproducing ===
    2525
    26 I reduced this down to two clean Django 4.0.2 setups, the only changes are adding `INSTALLED_APPS` `django_celery_results` and configuring `DATABASES`.
     26I reduced this down to two clean Django 4.0.2 setups, the only changes are adding `INSTALLED_APPS` `django_celery_results`, and configuring `DATABASES` for Oracle and PostgreSQL respectively.
    2727
    28 By running `makemigrations` on each in turn, they generate new migrations.
     28By running `makemigrations` on each in turn, they generate new migrations every time.
    2929
    3030{{{
Back to Top