W 1.8 1.8.1迁移问题

试图将Wagtail从1.7升级到1.8.1，但运行迁移时出现以下错误。我们正在使用Postgres数据库。W 1.8 1.8.1迁移问题

Applying wagtailimages.0016_deprecate_rendition_filter_relation...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 367, in execute_from_command_line 
    utility.execute() 
    File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 359, 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 294, in run_from_argv 
    self.execute(*args, **cmd_options) 
    File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 345, in execute 
    output = self.handle(*args, **options) 
    File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/migrate.py", line 204, in handle 
    fake_initial=fake_initial, 
    File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", line 115, in migrate 
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial) 
    File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/executor.py", line 145, 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 244, in apply_migration 
    state = migration.apply(state, schema_editor) 
    File "/usr/local/lib/python2.7/dist-packages/django/db/migrations/migration.py", line 129, 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 204, 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 495, 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 117, in _alter_field 
    new_db_params, strict, 
    File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", line 649, in _alter_field 
    params, 
    File "/usr/local/lib/python2.7/dist-packages/django/db/backends/base/schema.py", line 112, 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 94, 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.IntegrityError: could not create unique index "wagtailimages_rendition_image_id_742f4fe4119535f1_uniq" 
DETAIL: Key (image_id, filter_id, focal_point_key)=(507, 4, 2617-1240-3472x35) is duplicated.

下面是从PSQL命令的输出

Table "public.wagtailimages_rendition" 
    Column  |   Type   |        Modifiers 
-----------------+------------------------+-------------------------- -------------------------------------------- 
id    | integer    | not null default nextval('wagtailimages_rendition_id_seq'::regclass) 
filter_id  | integer    | 
file   | character varying(100) | not null 
width   | integer    | not null 
height   | integer    | not null 
image_id  | integer    | not null 
focal_point_key | character varying(255) | not null 
filter_spec  | character varying(255) | not null 
Indexes: 
    "wagtailimages_rendition_pkey" PRIMARY KEY, btree (id) 
    "wagtailimages_rendition_image_id_323c8fe0_uniq" UNIQUE CONSTRAINT, btree (image_id, filter_spec, focal_point_key) 
    "wagtailimages_rendition_58c64917" btree (filter_spec) 
    "wagtailimages_rendition_filter_id" btree (filter_id) 
    "wagtailimages_rendition_filter_spec_1cba3201_like" btree (filter_spec varchar_pattern_ops) 
    "wagtailimages_rendition_image_id" btree (image_id) 
Foreign-key constraints:

从SQL导入的错误是PSQL：foxtail.sql：68823：输出后的新鲜进口，但在运行前

ERROR: constraint "wagtailcore__content_type_id_c28424df_fk_django_content_type_id" for relation "wagtailcore_page" already exists 
psql:foxtail.sql:68831: ERROR: constraint "wagtailcore_collection_id_5423575a_fk_wagtailcore_collection_id" for relation "wagtailcore_groupcollectionpermission" already exists 
ALTER TABLE 
psql:foxtail.sql:68847: ERROR: constraint "wagtailcore_groupc_permission_id_1b626275_fk_auth_permission_id" for relation "wagtailcore_groupcollectionpermission" already exists 
psql:foxtail.sql:68855: ERROR: constraint "wagtailcore_groupcollectionp_group_id_05d61460_fk_auth_group_id" for relation "wagtailcore_groupcollectionpermission" already exists 
ALTER TABLE 
ALTER TABLE 
ALTER TABLE 
ALTER TABLE 
ALTER TABLE 
psql:foxtail.sql:68903: ERROR: constraint "wagtaildocs_collection_id_23881625_fk_wagtailcore_collection_id" for relation "wagtaildocs_document" already exists 
psql:foxtail.sql:68911: ERROR: constraint "wagtaildocs_docume_uploaded_by_user_id_17258b41_fk_auth_user_id" for relation "wagtaildocs_document" already exists 
ALTER TABLE 
psql:foxtail.sql:68927: ERROR: constraint "wagtailimag_collection_id_c2f8af7e_fk_wagtailcore_collection_id" for relation "wagtailimages_image" already exists

迁移

Table "public.wagtailimages_rendition" 
Column  |   Type   |         Modifiers 
-----------------+------------------------+-------------------------- -------------------------------------------- 
id    | integer    | not null default nextval('wagtailimages_rendition_id_seq'::regclass) 
filter_id  | integer    | not null 
file   | character varying(100) | not null 
width   | integer    | not null 
height   | integer    | not null 
image_id  | integer    | not null 
focal_point_key | character varying(255) | not null 
Indexes: 
"wagtailimages_rendition_pkey" PRIMARY KEY, btree (id) 
"wagtailimages_rendition_image_id_742f4fe4119535f1_uniq" UNIQUE CONSTRAINT, btree (image_id, filter_id, focal_point_key) 
"wagtailimages_rendition_filter_id" btree (filter_id) 
"wagtailimages_rendition_image_id" btree (image_id) 
Foreign-key constraints: 
"filter_id_refs_id_6909da8c" FOREIGN KEY (filter_id) REFERENCES wagtailimages_filter(id) DEFERRABLE INITIALLY DEFERRED 
"image_id_refs_id_e221c01d" FOREIGN KEY (image_id) REFERENCES wagtailimages_image(id) DEFERRA:

来源

2017-02-21 joss

我对这个错误有些困惑，因为有问题的迁移应该是删除有问题的唯一索引，而不是创建它......请你可以在Postgresql命令行上运行'\ d wagtailimages_rendition'并粘贴在这里输出，所以我可以看到数据库表当前处于什么状态？ – gasman

我们在本地开发中使用docker，当我在删除容器后再次尝试时，迁移运行正常。当我试图导入某些sql以用一些数据填充数据库时，出现错误，我在管理员中拥有的所有内容都默认为欢迎使用您的w site站点页面。虽然它已经导入了用户等。似乎如果有数据已经存在，迁移失败。 – joss

看起来您的SQL导入文件包含一些模式更改/创建命令，这些命令在迁移时肯定不会很好，因为它依赖于从一个特定的初始数据库状态开始。我猜想它的目的是从一个空的数据库开始运行 - 完成没有错误吗？如果是这样，那么如果在此之后运行Wagtail 1.8.1迁移，会发生什么？ – gasman

既然不能让情况怎么上面出现的感觉，我只能建议“核选项”：由PostgreSQL的命令行运行

DELETE FROM wagtailimages_rendition;

删除wagtailimages_rendition表的内容。这应该允许剩余的迁移完成而没有错误。这将不会导致持续的数据丢失，因为W will将在需要它们时重新生成翻译 - 尽管页面请求一段时间会更慢，因为它必须重新呈现每个映像丢失了翻译条目的地方。

UPDATE：而不是删除一切，更保守的方法是找到并删除重复记录：

DELETE FROM wagtailimages_rendition 
WHERE image_id || '-' || filter_id || '-' || focal_point_key IN (
    SELECT image_id || '-' || filter_id || '-' || focal_point_key 
    FROM (
     SELECT image_id, filter_id, focal_point_key, COUNT(*) AS count 
     FROM wagtailimages_rendition GROUP BY image_id, filter_id, focal_point_key 
    ) AS renditions 
    WHERE count > 1 
);

来源

2017-02-21 16:51:05 gasman

谢谢，这工作。 – joss

在制作过程中，我们不确定是否需要添加我们的再现表，不仅仅是因为性能，而是因为外部系统调用w to以生成在django模板之外使用的设置大小的图像，所以它们将永远不会以同样的方式再次调用在页面上使用的图像将是。（如果这是有道理的？）我发现了这个问题，Karl在这个问题中发布了这一点，https://github.com/wagtail/wagtail/issues/685删除了重复的表示。我在本地尝试过，它允许迁移继续。你认为这会是一个选择吗？谢谢Joss – joss

@joss是的，这应该工作。我认为你可能需要修改Karl的SQL以在唯一性标准中包含'focal_point_key'，以使其与当前模式保持同步 - 我已经更新了我的答案以包含（未经测试的）固定SQL。 – gasman

我可以证实什么乔斯是看到在这一侧。

我猜测出于某种原因，我们比其他人拥有更长的focal_point_key值，否则每个人在迁移时都会看到这个问题。

难道这是因为你过去为我们做过的一些习惯性工作吗？

不知道现在解决方案在这里，任何帮助，非常感谢。

来源

2017-02-28 14:08:34 user2160823

W 1.8 1.8.1迁移问题

回答

相关问题