Django : ProgrammingError: column "id" does not exist[英] Django : ProgrammingError: column "id" does not exist

本文是小编为大家收集整理的关于Django : ProgrammingError: column "id" does not exist的处理方法,想解了Django : ProgrammingError: column "id" does not exist的问题怎么解决?Django : ProgrammingError: column "id" does not exist问题的解决办法?那么可以参考本文帮助大家快速定位并解决问题。

问题描述

我尝试使用postgresql数据库(在我拥有sqlite之前),但是当我执行python manage.py migrate>:

时,我有一条消息
Operations to perform:
Apply all migrations: sessions, admin, sites, auth, contenttypes, main_app
Running migrations:
Rendering model states... DONE
Applying main_app.0004_auto_20161002_0034...Traceback (most recent call last):
File "manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 353, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 345, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 348, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 399, in execute
output = self.handle(*args, **options)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", line 200, in handle
executor.migrate(targets, plan, fake=fake, fake_initial=fake_initial)
File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", line 92, in migrate
self._migrate_all_forwards(plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", line 121, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", line 198, in apply_migration
state = migration.apply(state, schema_editor)
File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/migration.py", line 123, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/operations/fields.py", line 201, in database_forwards
schema_editor.alter_field(from_model, from_field, to_field)
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", line 482, in alter_field
old_db_params, new_db_params, strict)
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/postgresql/schema.py", line 110, in _alter_field
new_db_params, strict,
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", line 634, in _alter_field
params,
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", line 110, in execute
cursor.execute(sql, params)
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 79, in execute
return super(CursorDebugWrapper, self).execute(sql, params)
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line 95, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/local/lib/python2.7/dist-packages/django/db/backends/utils.py", line 64, in execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: column "id" does not exist
LINE 1: ..._app_projet" ALTER COLUMN "id" TYPE integer USING "id"::inte...

所以我想这个错误是关于我的模型" projet",但是此模型具有ID字段!我在 0001_Initial.py 中看到,

...
migrations.CreateModel(
        name='Projet',
        fields=[
            ('id', models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID')),
            ('name', models.CharField(db_index=True, max_length=30)),
            ('presentation', models.TextField(max_length=2500, null=True)),
...

我的迁移main_app.0004_auto_20161002_0034:

class Migration(migrations.Migration):

    dependencies = [
        ('main_app', '0003_auto_20161002_0033'),
    ]

    operations = [
        migrations.AlterField(
            model_name='projet',
            name='id',
            field=models.AutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
    ),
    ]

projet模型就是这样:

class Group(models.Model) :
    name = models.CharField(max_length=30, db_index=True)

    class Meta :
        abstract = True
        unique_together = (("id", "name"),)


class Projet(Group) :
    presentation = models.TextField(max_length=2500, null=True)

真的,我不明白为什么我有这个错误...我的设置配置数据库很好,所有其他模型都可以工作,...

如果我忘记了一些东西,请随时告诉我!我真的需要您的帮助!

推荐答案

您的模型定义没有将任何字段识别为主键,因此Django假定一个名为id的主键列.但是,该列实际上并不存在于表中.

更改您的模型定义以将其中一个字段指定为主要键,而Django不会尝试寻找id列.

其他推荐答案

class Group(models.Model) :
    name = models.CharField(max_length=30, unique=True)

    class Meta:
        abstract = True


class Projet(Group) :
    presentation = models.CharField(max_length=2500, blank=True)  

删除您的迁移并创建一个新的迁移.

只添加我的两美分.

无效字段:

避免在基于字符串的字段上使用NULL,例如Charfield和 textfield,因为空字符串值将始终存储为空 琴弦,不像无效.如果基于字符串的字段的null = true,那 表示"无数据"具有两个可能的值:空和空 细绳.在大多数情况下,拥有两个可能的值 "没有数据;" Django约定是使用空字符串,而不是null.

参见 https://docs.djangoproject.com/en/1.10/ref/models/fields/#null

max_length:

如果指定了max_length属性,它将反映在 自动生成表单字段的Textarea小部件.但是不是 在模型或数据库级别执行.为此使用Charfield.

/ref/models/fields/#textfield

其他推荐答案

如果缺少ID列,只需在Postgres本身中添加列.转到PGADMIN,而不是到表格,在那里创建列ID.

回到django makemigrations,而不是迁移.如果这将失败,请删除应用程序迁移文件夹中的所有内容,而没有 init .py并删除文件夹中的所有内容 pycache

比迁移的makemigrations,它应该起作用.

本文地址:https://www.itbaoku.cn/post/1763743.html