Django 1.8 OperationalError: no such column:

Question

I'm using django 1.8 and I'm having problems adding to my models.py. Currently it's:

from django.db import models


# Create your models here.
class Company(models.Model):
    role = models.CharField(max_length=32, blank=True)
    name = models.CharField(max_length=70, blank=True)

and it works perfectly fine but whenever I try to add to this and then run the server I get

OperationalError: no such column [added element]

For example I added founder = models.CharField(max_length=200, blank=True) and I ran the program and I got

django.db.utils.OperationalError: no such column: companies_company.founder

Dima Kudosh · Accepted Answer · 2015-08-05T21:05:19.463

4

Run in your console this commands:

manage.py makemigrations app_name
manage.py migrate app_name

Every time when you change model in your app you should migrate changes to your db using makemigration and migrate commands. When you adding a new column to your db table you must add value of this column to all existing rows. You can do it by seting default value in your new field in your model. Or set values when run migrate command ( django automatically propose this) You can read about this in docs

edited Aug 05 '15 at 21:05

answered Aug 05 '15 at 20:26

Dima Kudosh

7,126
4
36
46

1

What django print in console when you ran makemihration and migrate commands – Dima Kudosh Aug 05 '15 at 20:38
The exact error is too long to post here but the important part at the end is "django.db.utils.OperationalError: no such column: companies_company.founder" – Soroush Ghodsi Aug 05 '15 at 20:40
When you add new column you should set default value to your field in model or set values for all existing rows in migrate command – Dima Kudosh Aug 05 '15 at 20:43
What do you mean? How can I do that? – Soroush Ghodsi Aug 05 '15 at 20:44
founder = models.CharField(max_length=200, blank=True, default='something') or when you run manage.py migrate app_name django will show you message that you must set default values for existing raws and it run python console where you can do this – Dima Kudosh Aug 05 '15 at 20:48
Maybe you should turn that into a answer to the question also maybe you can explain a but more. – Soroush Ghodsi Aug 05 '15 at 20:51
I don't know what to set default to. – Soroush Ghodsi Aug 05 '15 at 20:58
What should 'something' be? – Soroush Ghodsi Aug 05 '15 at 21:09
You make something wrong, makemigrations can't throw this exception. Are you sure that you migrate correct app? – Dima Kudosh Aug 05 '15 at 21:09
I am certain it is this app. it is my only app. – Soroush Ghodsi Aug 05 '15 at 21:10
'Something' it default value which saved in your db. And if you already have data in your db(this data without your new column) it add new column and set this default value('something') to all existing data – Dima Kudosh Aug 05 '15 at 21:13
How can I find this default value? – Soroush Ghodsi Aug 05 '15 at 21:14
It bad solution but it's must work. Just drop your db and run manage.py syncdb again. – Dima Kudosh Aug 05 '15 at 21:15
How do I drop my db? Btw thank you for helping thus far – Soroush Ghodsi Aug 05 '15 at 21:16
You set default value when create field to your model. Your new field is charfield it seems that default value must be any string you want – Dima Kudosh Aug 05 '15 at 21:17
What db you are using? – Dima Kudosh Aug 05 '15 at 21:18
2

Simply delete file with you database. If you don't change settings.py it should be named as mydatabase.sqlite and placed in project root directory. And again run syncdb. – Dima Kudosh Aug 05 '15 at 21:24
I too got the same error, and `makemigrations` , ` migrate` didn't work. I read the docs and I understand that, it should actually work. What can be the possible reason? – Jithin Pavithran Jun 24 '16 at 06:19

Naveen · Answer 2 · 2017-11-08T09:45:56.110

This type of problem occurs when there are some operations on the model field in some other files such as forms.py or views.py other than models.py when you run makemigrations. If you read the traceback carefully you can figure it out from which file the problem is originating.

For example, if the traceback tells you some complaints in forms.py which may happen to use some of the model fields, just comment out the code that is working on the model fields and rerun makemigrations again. Hopefully it resolves the issue.

If it does, you can then remove the comments that you added before.

score 0 · Answer 3 · answered Aug 05 '15 at 20:26

0

You have to re sync the database using python manage.py makemigrations

answered Aug 05 '15 at 20:26

Obj3ctiv3_C_88

1,478
1
17
29

score 0 · Answer 4 · edited May 03 '20 at 17:12

Maybe not optimal, but it worked for me doing that (and the default thing did not work):

delete all files apart from the init.py in migrations folder
delete the db.sqlite file
doing: python manage.py runserver (without this one previous to migrate, migrations, that did not work, I think it's linked to the views / templates calling tags, so has to run first)

python manage.py migrate
python manage.py makemigrations
python manage.py migrate
python manage.py runserver
python manage.py createsuperuser

score -1 · Answer 5 · answered May 09 '19 at 16:55

-1

I found that clearing all data with python3 manage.py sqlflush and then python3 manage.py flush

Then makemigrations, sqlmigrate, and then migrate

It will delete all data in the SQL database including users and objects

answered May 09 '19 at 16:55

Raccoondude

21
2

Django 1.8 OperationalError: no such column:

5 Answers5

Linked