[Fixed]-Django migration relation does not exist

26๐Ÿ‘

I had this problem and I had to comment out everything in urls.py that referenced views.py, then run makemigrations.

๐Ÿ‘คMattchoo

15๐Ÿ‘

Make sure that you donโ€™t have any class variables in your code that are calling Django manager

For example:

class SomeViewSet(viewsets.ViewSet):
    se = SomeEntity.objects.first()  # fetching some entity on the class level

    def list(self, request):
    # the rest of the code

So, when you try to create/apply migrations, this variable will also try to initialise, and will try to access SomeEntity, but at that moment that entity doesnโ€™t even exist, and the error occurs.

๐Ÿ‘คbandakoo

3๐Ÿ‘

Try to migrate particular app using following process. Refer Django migrations

python manage.py makemigrations

Initial migration created then run migrate command with app name

python manage.py migrate appname1, appname2
๐Ÿ‘คNIKHIL RANE

3๐Ÿ‘

If all other solutions mentioned fail, if you are still in development probably the easiest solution is dropping the database (in pgAdmin 4 2.0, right-click on database) and then run makemigrations and migrate.

๐Ÿ‘คPHPirate

2๐Ÿ‘

When you run a query before applying migrations this error appears.

If you got this error during python manage.py makemigrations or python manage.py migrate you must consider that makemigrations and migrate commands run after successful django bootstrap! So this error happens when you run a query during django bootstrap! So you must find the place you run this query during bootstrap progress.

For example, during bootstrap, django reads root {project}/urls.py and its nested imports. If you use views or viewsets in urls.py and they are run a query during initializing (in their __init__ method or __init__.pyfile or somewhere etc.), it happens!

In this situation and similars, you must comment out any entry in urls.py and similar files which cause running a query during bootstrap and prevent them from running by raising of exception during bootstrap! makemigrations and migrate need successful bootstrap to be run!

If your commented out code needs to makemigrations and migrate handcooks :D, it needs to be patient and be silent for a cycle or a while ;), and after a successful migrations it could be active and verbose ;D.

๐Ÿ‘คAbdolHosein

1๐Ÿ‘

Your app is trying to call some DB entries that does not exist.
If you are trying to migrate it to a new database, one of your options is to export a dump of old database and import it to your new DB.

For example in PostgreSQL, import the database using below command then migration will work!

sudo -u postgres -i psql mydb < mydb-export.sql

1๐Ÿ‘

Django is running an optional check. Pass the --skip-checks flag in your call to manage.py.

0๐Ÿ‘

If youโ€™re running in local,
For each Django app (maybe you have only one), erase the content of the migrations folder.
Then, run python manage.py makemigrations app1 app2 app3 (if you have 3 Django apps named app1, app2, app3). This will (re)create the migrations files required to migrate your database

Then, run python manage.py migrate. It will apply the migration files you just created.

๐Ÿ‘คDavid Dahan

0๐Ÿ‘

This error may be related to previous database error. So if you created a new database and you also face that type of error, you can simply run the command with the app name:

python manage.py makemigrations <"app name">
python manage.py migrate <"app name">
๐Ÿ‘คParamjeet

0๐Ÿ‘

First remove all urls from urls.py.

Create simple function view for viewing nothing:

def simple(request):
    context = {}
    return render(request, 'base.html', context)

and add urls to urls.py

do migrate:

python manage.py migrate

after migrate, recover the deleted urls.py contents

๐Ÿ‘คminsu kim

0๐Ÿ‘

For me the error came from some initialization code I put into the app.ready() method. Commenting that part of code allowed me to run the command makemigrations without any issue.

I believe app.ready is called at some point by manage.py even for the makemigrations command, which caused my code to query my database before any migration.

I found the problematic code thanks to the traceback.

๐Ÿ‘คPleaseHelp

Leave a comment