You should first set your current state to 0003 with –fake (assuming 0003 is the last migration you really have applied): python manage.py migrate –fake core 0003 And then proceed as usual: python manage.py migrate core Relevant documentation: https://docs.djangoproject.com/en/dev/ref/django-admin/#migrate
The answer is: apps.get_model(‘contenttypes’, ‘ContentType’) 🙂 Needed it myself today.
This works, with a minor caveat: Django will no longer know that the renamed migration is applied. So the steps to renaming a migration are: Rename the file. Repoint any dependencies to the new file. If the renamed migration was already applied, apply it again using –fake. If it’s a brand new migration, 2 and … Read more
One way: The best way I found to do this is using RunSQL: Migrations contains the RunSQL class. To do this: ./manage.py makemigrations –empty myApp edit the created migrations file to include: operations = [ migrations.RunSQL(‘RAW SQL CODE’) ] As Nathaniel Knight mentioned, RunSQL also accepts a reverse_sql parameter for reversing the migration. See the … Read more
This worked for me. I thank my coworker for sharing this knowledge after I searched online for many hours. Start your db shell python manage.py dbshell Use the database you want. If you don’t know, run .databases (SQLite) or SHOW databases mysql>use <database_name>; Retrieve all the migrations under your app mysql> select * from django_migrations … Read more
If you’re on 1.7, use python manage.py migrate –list. (docs) If you’re on 1.8 or above, use python manage.py showmigrations –list. (docs) In either case, there will be an [X] to show which migrations have been applied.
The Django doc makes it clear: When writing a RunPython function that uses models from apps other than the one in which the migration is located, the migration’s dependencies attribute should include the latest migration of each app that is involved, otherwise you may get an error similar to: LookupError: No installed app with label … Read more
You can create a manual migration by running the command: python manage.py makemigrations app_name –name migration_name –empty Where app_name corresponds to the app within your project you want to add the migration. Remember Django manages both Project and Apps (A project is a collection of configuration and apps for a particular website. A project can … Read more
You haven’t run manage.py makemigrations customuser to create the migrations for your CustomUser app. Also, you haven’t run any of the existing migrations – you should do manage.py migrate.
Just an update for those who’ll encounter this question (from Google or whatever else)… Currently Django has a simple “proper way” to define model without managing database tables: Options.managed Defaults to True, meaning Django will create the appropriate database tables in syncdb and remove them as part of a reset management command. That is, Django … Read more