Django迁移：django.db.utils.OperationalError：没有这样的列：

Question

Whenever I add a new column to my model I get:

django.db.utils.OperationalError: no such column: companies_company.[name of added column]

For example, I just added "employee_count" and whenever I run

python manage.py makemigrations

I get:

django.db.utils.OperationalError: no such column: companies_companyadmin.employee_count

My model.py looks like this:

from django.db import models

import csv

class Company(models.Model):
   name = models.CharField(max_length=70, blank=True)
   description = models.CharField(max_length=1200, blank=True)
   employee_count = models.IntegerField(blank=True)


class CompanyAdmin(models.Model):
    name = models.CharField(max_length=70, blank=True)
    description = models.CharField(max_length=1200, blank=True)
    employee_count = models.(blank=True)

with open("organizationTest.txt","rU") as f:
        reader = csv.reader(f)
        for row in reader:
            _, created = Company.objects.get_or_create(
                name=row[3].decode('latin-1').encode('utf8'),
                description=row[15].decode('latin-1').encode('utf8'),
                )

The CSV part is simply to populate my DB (I should probably do it somewhere else).

And my admin.py:

from django.contrib import admin
from .models import Company


class CompanyAdmin(admin.ModelAdmin):
    pass


admin.site.register(Company, CompanyAdmin)

This also happens when I try to run the server or "syncdb".

If anyone knows why this is happening and how I could fix this I would love to know! Thanks in advance! I'm happy to answer any questions you may have.

Answer 1

In my case I had an initial value in some Querysets of an updated model. When I removed these initial statements, makemigrations had worked.

Answer 2

Appears my original answer wasn't clear enough.

Company.objects.get_or_create( name=row[3].decode('latin-1').encode('utf8'), description=row[15].decode('latin-1').encode('utf8'), )

This block is out of a class so it runs when the server is started or basically everytime manage.py is run. Company.objects.get_or_create(...) is trying to run, on the updated database model that can't be created yet. To make the migrations you have to comment this line out, then make the migrations, then it will work.