Django - makemigrations - No changes detected

Question

I was trying to create migrations within an existing app using the makemigrations command but it outputs  No changes detected    Usually I create new apps using the startapp command but did not use it for this app when I created it   After debugging  I found that it is not creating migration because the migrations package folder is missing from an app    Would it be better if it creates the folder if it is not there or am I missing something

User · Answer

I ve read many answers to this question often stating to simply run makemigrations in some other ways  But to me  the problem was in the Meta subclass of models   I have an app config that says label    lt app name gt   in the apps py file  beside models py  views py etc   If by any chance your meta class doesn t have the same label as the app label  for instance because you are splitting one too big app into multiple ones   no changes are detected  and no helpful error message whatsoever   So in my model class I have now   class ModelClassName models Model        class Meta          app label     lt app name gt      lt -- this label was wrong before       field name   models FloatField             Running Django 1 10 here

User · Answer

In my case i forgot to insert the class arguments  Wrong   class AccountInformation      Correct  class AccountInformation models Model

User · Answer

I solved that problem by doing this    Erase the  db sqlite3  file  The issue here is that your current data base will be erased  so you will have to remake it again  Inside the migrations folder of your edited app  erase the last   updated file  Remember that the first created file is   0001 initial py   For example  I made a new class and register it by the  makemigrations  and  migrate  procedure  now a new file called  0002 auto etc py  was created  erase it  Go to the  pycache  folder  inside the migrations folder  and erase the file  0002 auto etc pyc   Finally  go to the console and use  python manage py makemigrations  and  python manage py migrate

User · Answer

There are multiple possible reasons for django not detecting what to migrate during the makemigrations command    migration folder You need a migrations package in your app  INSTALLED APPS You need your app to be specified in the INSTALLED APPS  dict Verbosity  start by running makemigrations -v 3 for verbosity  This might shed some light on the problem  Full path In INSTALLED APPS it is recommended to specify the full module app config path  apply apps MyAppConfig  --settings you might want to make sure the correct settings file is set  manage py makemigrations --settings mysite settings  specify app name explicitly put the app name in manage py makemigrations myapp - that narrows down the migrations for the app alone and helps you isolate the problem   model meta check you have the right app label in your model meta  Debug django debug django core script  makemigrations command is pretty much straight forward  Here s how to do it in pycharm  change your script definition accordingly  ex  makemigrations --traceback myapp    Multiple databases    Db Router when working with django db router  the router class  your custom router class  needs to implement the allow syncdb method       makemigrations always creates migrations for model changes  but if   allow migrate   returns False

User · Answer

When adding new models to the django api application and running the python manage py makemigrations the tool did not detect any new models   The strange thing was that the old models did got picked by makemigrations  but this was because they were referenced in the urlpatterns chain and the tool somehow detected them  So keep an eye on that behavior   The problem was because the directory structure corresponding to the models package had subpackages and all the   init   py files were empty  They must explicitly import all the required classes in each subfolder and in the models   init   py for Django to pick them up with the makemigrations tool   models    --   init   py           lt --- empty    -- patient         --   init   py       lt --- empty         -- breed py         --        -- timeline         --   init   py       lt -- empty         -- event py         --

User · Answer

My problem with this error  was that I had included  class Meta     abstract   True  Inside model that I wanted to creation migrate for

User · Answer

Well  I m sure that you didn t set the models yet  so what dose it migrate now     So the solution is setting all variables and set Charfield  Textfield        and migrate them and it will work

User · Answer

To create initial migrations for an app  run makemigrations and specify the app name  The migrations folder will be created     manage py makemigrations  lt myapp gt    Your app must be included in INSTALLED APPS first  inside settings py

User · Answer

This might hopefully help someone else  as I ended up spending hours trying to chase this down   If you have a function within your model by the same name  this will remove the value  Pretty obvious in hindsight  but nonetheless   So  if you have something like this   class Foobar models Model                 something   models BooleanField default False                 def something self           return  some logic    In that case  the function will override the setting above  making it  invisible  to makemigrations

User · Answer

I know this is an old question but I fought with this same issue all day and my solution was a simple one   I had my directory structure something along the lines of     apps     app          init   py       app sub1               init   py            models py       app sub2               init   py            models py       app sub3               init   py            models py    app2          init   py       app2 sub1               init   py            models py       app2 sub2               init   py            models py       app2 sub3               init   py            models py     main app          init   py       models py   And since all the other models up until the one I had a problem with were being imported somewhere else that ended up importing from main app which was registered in the INSTALLED APPS  I just got lucky that they all worked   But since I only added each app to INSTALLED APPS and not the app sub  when I finally added a new models file that wasn t imported ANYWHERE else  Django totally ignored it    My fix was adding a models py file to the base directory of each app like this      apps     app          init   py       models py  lt  lt  lt  lt  lt  lt  lt  lt  lt  lt --------------------------       app sub1               init   py            models py       app sub2               init   py            models py       app sub3               init   py            models py    app2          init   py       models py  lt  lt  lt  lt  lt  lt  lt  lt  lt  lt --------------------------       app2 sub1               init   py            models py       app2 sub2               init   py            models py       app2 sub3               init   py            models py     main app          init   py       models py   and then add from apps app app sub1 import   and so on to each of the app level models py files   Bleh    this took me SO long to figure out and I couldn t find the solution anywhere    I even went to page 2 of the google results   Hope this helps someone

User · Answer

A very dumb issue you can have as well is to define two class Meta in your model  In that case  any change to the first one won t be applied when running makemigrations    class Product models Model       somefield   models CharField max length 255      someotherfield   models CharField max length 255       class Meta          indexes    models Index fields   somefield    name  somefield idx         def somefunc self           pass        Many lines         class Meta          indexes    models Index fields   someotherfield    name  someotherfield idx

User · Answer

The solution is you have to include your app in INSTALLED APPS   I missed it and I found this same issue   after specifying my app name migration became successful    INSTALLED APPS          django contrib admin        django contrib auth        django contrib contenttypes        django contrib sessions        django contrib messages        django contrib staticfiles        boards         please note I mentioned boards in last  which is my app name

User · Answer

The Best Thing You can do is  Delete the existing database  In my case  I were using phpMyAdmin SQL database  so I manually delete the created database overthere    After Deleting  I create database in PhpMyAdmin  and doesn t add any tables   Again run the following Commands   python manage py makemigrations  python manage py migrate  After These Commands   You can see django has automatically created other necessary tables in Database Approx there are 10 tables    python manage py makemigrations  lt app name gt   python manage py migrate  And Lastly  After above commands all the model table  you have created are directly imported to the database   Hope this will help

User · Answer

My problem  and so solution  was yet different from those described above    I wasn t using models py file  but created a models directory and created the my model py file there  where I put my model  Django couldn t find my model so it wrote that there are no migrations to apply    My solution was  in the my app models   init   py file I added this line  from  my model import MyModel

User · Answer

There are sometimes when   manage py makemigrations is superior to   manage py makemigrations  lt myapp gt  because it can handle certain conflicts between apps    Those occasions occur silently and it takes several hours of swearing to understand the real meaning of the dreaded No changes detected message    Therefore  it is a far better choice to make use of the following command     manage py makemigrations  lt myapp1 gt   lt myapp2 gt       lt myappN gt

User · Answer

Make sure your app is mentioned in installed apps in settings py Make sure you model class extends models Model

User · Answer

One more edge case and solution    I added a boolean field  and at the same time added an  property referencing it  with the same name  doh   Commented the property and migration sees and adds the new field  Renamed the property and all is good

User · Answer

It is a comment but should probably be an answer   Make sure that your app name is in settings py INSTALLED APPS otherwise no matter what you do it will not run the migrations   INSTALLED APPS          django contrib admin        django contrib auth        django contrib contenttypes        django contrib sessions        django contrib messages        django contrib staticfiles         blog       Then run     manage py makemigrations blog

User · Answer

You should add polls apps PollsConfig to INSTALLED APPS in setting py

User · Answer

Another possible reason is if you had some models defined in another file  not in a package  and haven t referenced that anywhere else    For me  simply adding from  graph model import   to admin py  where graph model py was the new file  fixed the problem

User · Answer

First of all  make sure your app is registered in the Installed app in the setting py  Then the above answer works perfectly fine

User · Answer

I forgot to put correct arguments   class LineInOffice models Model       here     addressOfOffice   models CharField                max length  200     and here           in models py and then it started to drop that annoying  No changes detected in app  myApp

User · Answer

Try registering your model in admin py  here s an example - admin site register YourModelHere   You can do the following things -  1  admin site register YourModelHere    In admin py   2  Reload the page and try again  3  Hit CTRL-S and save  4  There might be an error  specially check models py and admin py  5  Or  at the end of it all just restart the server

User · Answer

I had another problem not described here  which drove me nuts   class MyModel models Model       name   models CharField max length 64  null True     works     language code   models CharField max length 2  default  en      works     is dumb   models BooleanField default False      doesn t work   I had a trailing     in one line perhaps from copy amp paste  The line with is dumb doesn t created a model migration with    manage py makemigrations  but also didn t throw an error  After removing the     it worked as expected    So be careful when you do copy amp paste  -

User · Answer

My problem was much simpler than the above answers and probably a far more common reason as long as your project is already set up and working   In one of my applications that had been working for a long time  migrations seemed wonky  so in a hurry  I did the following   rm -r   migrations   rm db sqlite3 python3 manage py makemigrations No changes detected   Whaat    I had mistakenly also removed all the   init   py files    - Everything was working again after I went in and   touch ads1 migrations   init   py   For each of my applications then the makemigrations worked again   It turns out that I had manually created a new application by copying another and forgot to put the   init   py in the migrations folder and that confinved me that everything was wonky - leading my making it worse with an rm -r as described above   Hope this helps someone from swearing at the  No changes detected  error for a few hours

User · Answer

INSTALLED APPS           blog apps BlogConfig        django contrib admin        django contrib auth        django contrib contenttypes        django contrib sessions        django contrib messages        django contrib staticfiles       make sure  blog apps BlogConfig    this is included in your settings py in order to make your app migrations  then run python3 manage py makemigrations blog or your app name

User · Answer

Another possibility is you squashed some migrations and applied the resulting one  but forgot to remove the replaces attribute from it

User · Answer

I had copied a table in from outside of django and the Meta class defaulted to  quot managed   false quot   For example  class Rssemailsubscription models Model       id   models CharField primary key True  max length 36              area   models FloatField  Area  Sq  KM    null True       class Meta          managed   False         db table    RSSEmailSubscription   By changing managed to True  makemigrations started picking up changes

User · Answer

I had a similar issue with django 3 0  according migrations section in the official documentation  running this was enough to update my table structure   python manage py makemigrations python manage py migrate   But the output was always the same   no change detected  about my models after I executed  makemigrations  script  I had a syntax error on models py at the model I wanted to update on db   field model   models CharField max length 255         instead of   field model   models CharField max length 255         Solving this stupid mistake  with those command the migration was done without problems  Maybe this helps someone

User · Answer

I had a different issue while creating a new app called deals  I wanted to separate the models inside that app so I had 2 model files named deals py and dealers py  When running python manage py makemigrations I got  No changes detected  I went ahead and inside the   init   py which lives on the same directory where my model files lived  deals and dealer  I did from  deals import   from  dealers import    And then the makemigrations command worked  Turns out that if you are not importing the models anywhere OR your models file name isn t models py then the models wont be detected  Another issue that happened to me is the way I wrote the app in settings py  I had  apps deals  It should ve been including the root project folder  cars apps deals

User · Answer

The possible reason could be deletion of the existing db file and migrations folder you can use python manage py makemigrations  lt app name gt  this should work  I once faced a similar problem

User · Answer

If you have the managed   True in yout model Meta  you need to remove it and do a migration  Then run the migrations again  it will detect the new updates

[python] Django - makemigrations - No changes detected

Examples related to python

Examples related to django

Examples related to django-migrations