#33566: Issue with migrations after upgrading Django 2 to Django 3.2.
-------------------------------------+-------------------------------------
Reporter: Ismael | Owner: nobody
Jerez |
Type: Bug | Status: new
Component: | Version: 3.2
Migrations | Keywords: orm, migrate,
Severity: Normal | makemigrations, database,
Triage Stage: | migrations, migration
Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Hi,
I recently upgraded from Django 2 to Django 3.2.
Everything works fine but when I execute “migrate” as a manage.py command,
it always says “Your models in app(s): ‘admin’, ‘auth’, ‘base’,
‘contenttypes’, ‘sessions’ have changes that are not yet reflected in a
migration, and so won’t be applied.
Run ‘manage.py makemigrations’ to make new migrations, and then re-run
‘manage.py migrate’ to apply them.”
If I execute “makemigrations” commands I always get “No changes detected”.
I downgrade to Django2, the message is gone.
I have every mentioned app on my INSTALLED_APPS variable in settings. As
you can see only ‘base’ app is one of mine, the rest are default Django
apps.
I am using Oracle 19 database that can not be recreated.
I hope you can help me or give me some ideas of what is happening and why
am I receiving that message from “migrate” command.
Thank you in advance,
Ismael.
--
Ticket URL: <https://code.djangoproject.com/ticket/33566>
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/0107017f69368b8b-f3acc6da-5f53-4124-ac22-10c9bcab85a2-000000%40eu-central-1.amazonses.com.
