#33566: Issue with migrations after upgrading Django 2 to Django 3.2.
-------------------------------------+-------------------------------------
Reporter: Ismael Jerez | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 3.2
Severity: Normal | Resolution: needsinfo
Keywords: orm, migrate, | Triage Stage:
makemigrations, database, | Unreviewed
migrations, migration |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => needsinfo
Comment:
Thanks for the reply Ismael.
> I test it removing these options so makemigrations generates new
migrations like reverting verbose_name to English but anyway when I run
migrate after that I still getting the message about changes not reflected
in a migration...
There are two things here I can't quite make sense of:
> I test it removing these options so makemigrations generates new
migrations like reverting verbose_name to English...
So this implies the `@no_translations` decorator is not working, so there
must be some customisation in your project affecting that.
> ... anyway when I run migrate after that I still getting the message
about changes not reflected in a migration...
As per my previous comment, I can get **both** commands to apply
translations but not just one of them, as you're seeing here. (Again,
there must be a customisation somewhere in your setup, one would think)
Can you provide a sample project, created using `startproject` and adding
just enough, to recreate the issue? Otherwise it's hard to see where the
error could be.
--
Ticket URL: <https://code.djangoproject.com/ticket/33566#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701814c7c3eb5-667eadda-17ec-43d9-8473-e76a7a0b2a63-000000%40eu-central-1.amazonses.com.
