Django 2.2.4 - “No migrations to apply” when run migrate after makemigrations

Question

I am trying to do a migration in django 2.2.4 in python 3.7. First I try to make do makemigations:

python3 manage.py makemigrations

I get:

Migrations for 'main':
  main/migrations/0001_initial.py
    - Create model TutorialCategory
    - Create model TutorialSeries
    - Create model Tutorial

But then I try the second step:

python3 manage.py migrate

I get:

Operations to perform:
  Apply all migrations: admin, auth, contenttypes, main, sessions
Running migrations:
  No migrations to apply.

Even though a migration should happen.

I tried deleting my migrations folder and then remaking it (with the empty __init__.py file inside) but it still doesn't work.

(Note: I have been following along the tutorial: Linking models with Foreign Keys - Django Web Development with Python p.9 by sentdex)

Is this all running locally? Not on Heroku, for example? – Daniel Roseman Aug 28 '19 at 19:15 — Daniel Roseman, Aug 28 '19 at 19:15
Yes it is running all locally. – user8802333 Aug 28 '19 at 19:18 — user8802333, Aug 28 '19 at 19:18

score 4 · Answer 1 · answered Apr 07 '20 at 13:19

4

I faced the same problem in django 2.2, The following worked for me...

delete the migrations folder resided inside the app folder
delete the pycache folder too
restart the server [if your server is on and you are working from another cli]
python manage.py makemigrations <app_name> zero
python manage.py makemigrations <app_name> [explicit app_name is important]
python manage.py migrate

answered Apr 07 '20 at 13:19

MASBHA NOMAN

145
1
11

On the command: "python manage.py makemigrations zero" What do this parameter 'zero' ? – Programadores Brasil May 19 '21 at 16:48
@ProgramadoresBrasil it just resets all migrations – MASBHA NOMAN Jul 15 '21 at 18:11

score 3 · Accepted Answer · answered Aug 28 '19 at 19:41

3

Somehow your migrations are virtually or faked applied in the database, Truncating django_migrations table should work.

Delete all the migrations files:

find . -path "/migrations/.py" -not -name "init.py" -delete find . -path "/migrations/.pyc" -delete
Truncate table:

truncate django_migrations
makemigrations, migrate.

answered Aug 28 '19 at 19:41

shivam singhal

156
4
9

4

what is 'truncate django_migrations'? – Alex M.M. Mar 24 '20 at 11:31
@AlexM.M. truncate is delete all entrys on the table django_migrations. – Programadores Brasil May 19 '21 at 16:47
1

`truncate django_migrations` gives an error. `truncate: you must specify either ‘--size’ or ‘--reference’ Try 'truncate --help' for more information.` – sequence Jun 04 '22 at 10:15

score 1 · Answer 3 · answered Oct 28 '21 at 04:35

w/in the app directory I deleted the pycache and migrations folders,

from django.migrations tables I deleted all rows like this for PostgreSQL

DELETE FROM public.django_migrations
WHERE public.django_migrations.app = 'target_app_name';

To delete any app tables already created for the tables to be created from scratch.

score 1 · Answer 4 · answered May 26 '22 at 23:10

1

Mine didn't migrate cause there was already a record in the django_migrations table with the same name, so I just removed it and then migrate worked.

answered May 26 '22 at 23:10

Axe

11
1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community May 27 '22 at 01:47

score 0 · Answer 5 · answered Aug 13 '23 at 21:35

In my case my settings.py file had two entries for the DATABASES setting.

The first one being my postgres setting

DATABASES = {"default": env.db()}
DATABASE_URL = env("DATABASE_URL")

The second one being the default sqlite configuration.

DATABASES = {
    "default": {
        "ENGINE": "django.db.backends.sqlite3",
        "NAME": BASE_DIR / "db.sqlite3",
    }
}

It is worth checking that your setting file has only one DATABASE setting with the correct configuration.

Django 2.2.4 - “No migrations to apply” when run migrate after makemigrations

5 Answers5