【问题标题】:Django 'Key(field)=() is duplicated'Django'键(字段)=()重复'
【发布时间】:2017-04-26 16:19:38
【问题描述】:

这个问题在here 之前被问过,但是针对不同的场景。

我正在开发一个 Django/Wagtail 项目。在某些时候,我不得不修改模型并添加一些字段。

我无意中为一个新字段添加了一个标志 unique=True。这样:

title = models.CharField(max_length=100, unique=True, blank=True, null=True, verbose_name=_('Category Title'))

在进行迁移和迁移时,它喊出了这个问题:

然后我意识到了错误,删除了 unique=True 并将其保留为:

title = models.CharField(max_length=100, blank=True, null=True, verbose_name=_('Category Title'))

我进行了迁移并再次迁移,希望问题会消失。但是我遇到了同样的问题。

我该如何解决这个问题?

这是最后一次迁移:

class Migration(migrations.Migration):

    dependencies = [
        ('distributed', '0029_remove_blogcategory_title'),
    ]

    operations = [
        migrations.AddField(
            model_name='blogcategory',
            name='title',
            field=models.CharField(blank=True, max_length=100, null=True, verbose_name='Category Title'),
        ),
    ]

这就是痕迹:

    Microsoft Windows [Versión 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Windows\system32>cd C:/

C:\>cd distributed

C:\distributed>cd distributed

C:\distributed\distributed>python manage.py runserver
Performing system checks...

System check identified no issues (0 silenced).

You have 6 unapplied migration(s). Your project may not work properly until you
apply the migrations for app(s): distributed.
Run 'python manage.py migrate' to apply them.
April 26, 2017 - 12:40:45
Django version 1.10.7, using settings 'genesis.settings.dev'
Starting development server at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.
^C
C:\distributed\distributed>python manage.py migrate
Operations to perform:
  Apply all migrations: admin, auth, contenttypes, distributed, otp_static, otp_
totp, otp_yubikey, sessions, sites, taggit, two_factor, wagtailadmin, wagtailcor
e, wagtaildocs, wagtailembeds, wagtailforms, wagtailimages, wagtailredirects, wa
gtailsearch, wagtailusers
Running migrations:
  Applying distributed.0025_auto_20170425_1827...Traceback (most recent call las
t):
  File "manage.py", line 11, in <module>
    execute_from_command_line(sys.argv)
  File "C:\Python27\lib\site-packages\django\core\management\__init__.py", line
367, in execute_from_command_line
    utility.execute()
  File "C:\Python27\lib\site-packages\django\core\management\__init__.py", line
359, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "C:\Python27\lib\site-packages\django\core\management\base.py", line 294,
 in run_from_argv
    self.execute(*args, **cmd_options)
  File "C:\Python27\lib\site-packages\django\core\management\base.py", line 345,
 in execute
    output = self.handle(*args, **options)
  File "C:\Python27\lib\site-packages\django\core\management\commands\migrate.py
", line 204, in handle
    fake_initial=fake_initial,
  File "C:\Python27\lib\site-packages\django\db\migrations\executor.py", line 11
5, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_i
nitial=fake_initial)
  File "C:\Python27\lib\site-packages\django\db\migrations\executor.py", line 14
5, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_
initial)
  File "C:\Python27\lib\site-packages\django\db\migrations\executor.py", line 24
4, in apply_migration
    state = migration.apply(state, schema_editor)
  File "C:\Python27\lib\site-packages\django\db\migrations\migration.py", line 1
29, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, projec
t_state)
  File "C:\Python27\lib\site-packages\django\db\migrations\operations\fields.py"
, line 84, in database_forwards
    field,
  File "C:\Python27\lib\site-packages\django\db\backends\postgresql\schema.py",
line 21, in add_field
    super(DatabaseSchemaEditor, self).add_field(model, field)
  File "C:\Python27\lib\site-packages\django\db\backends\base\schema.py", line 4
09, in add_field
    self.execute(sql, params)
  File "C:\Python27\lib\site-packages\django\db\backends\base\schema.py", line 1
12, in execute
    cursor.execute(sql, params)
  File "C:\Python27\lib\site-packages\django\db\backends\utils.py", line 79, in
execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "C:\Python27\lib\site-packages\cachalot\monkey_patch.py", line 111, in in
ner
    out = original(cursor, sql, *args, **kwargs)
  File "C:\Python27\lib\site-packages\django\db\backends\utils.py", line 64, in
execute
    return self.cursor.execute(sql, params)
  File "C:\Python27\lib\site-packages\django\db\utils.py", line 94, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "C:\Python27\lib\site-packages\django\db\backends\utils.py", line 64, in
execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: could not create unique index "distributed_blogc
ategory_title_key"
DETAIL:  Key (title)=() is duplicated.


C:\distributed\distributed>

【问题讨论】:

  • 刚刚添加它们
  • 回溯告诉你错误发生在distributed.0025_auto_20170425_1827 - 我不认为这是你展示的迁移。 python manage.py showmigrations distributed 的输出是什么?
  • 你是对的。这就是我的“新手”显而易见的地方。我认为新的迁移“覆盖”了旧的迁移。那么,我应该删除导致错误的迁移并重新运行 make 迁移吗?
  • 在删除任何迁移之前等待。如果您删除已经应用的迁移,那么让您的模型和数据库重新同步可能会非常困难。运行 python manage.py showmigrations distributed 以查看已应用的迁移。
  • 是的,没错。如果您删除 25-30(或备份它们以确保安全),然后运行 ​​makemigrationsmigrate 那么它应该可以工作。

标签: python django postgresql wagtail


【解决方案1】:

回溯告诉您,当您尝试运行迁移 0025 时发生错误。

python manage.py showmigrations 的输出告诉您迁移 0025-0030 尚未应用。

[X] 0022_auto_20170109_1620
[X] 0023_auto_20170109_1621
[X] 0024_auto_20170112_1933
[ ] 0025_auto_20170425_1827
[ ] 0026_auto_20170425_1829
[ ] 0027_auto_20170425_1839
[ ] 0028_auto_20170425_1840
[ ] 0029_remove_blogcategory_title
[ ] 0030_blogcategory_title

因此,删除这些迁移应该是安全的(为了安全起见,您可能需要备份它们)。然后,您可以重新运行 makemigrationsmigrate 以重新创建和运行新的迁移。

【讨论】:

    猜你喜欢
    • 2017-05-19
    • 2012-05-25
    • 2014-10-11
    • 1970-01-01
    • 2018-06-09
    • 2012-08-08
    • 2012-10-22
    • 2014-09-04
    • 2017-05-23
    相关资源
    最近更新 更多