Fix FEW undeletable images #5

New Issue

Soveia · 2022-11-20T17:35:46Z

Soveia commented

2022-11-20 17:35:46 +00:00

Certain images, such as https://fireemblemwiki.org/wiki/File:GCNRankAxe.gif cannot be deleted due to broken oldimage entries, specifically, they are lacking an oi_archive_name.

Running SELECT * FROM oldimage WHERE oi_archive_name = ""; returns a total of 794 images with this problem.

As this is not a high priority task and there is a risk of breaking things, we should do this the next time there is maintenance.

The way to fix this is to just remove these entries
DELETE FROM oldimage WHERE oi_archive_name ="";

Prior to doing this, we should take note of one of the affected images, and have a link to the exact contribution that uploaded it. This is to find out if referential integrity breaks or not. We may want to keep a backup of the affected rows afterwards for insurance, if a problem is later discovered.

This fix does not delete the actual live files, it merely fixes the cause of why they cannot be deleted.

Certain images, such as https://fireemblemwiki.org/wiki/File:GCNRankAxe.gif cannot be deleted due to broken oldimage entries, specifically, they are lacking an oi_archive_name. Running `SELECT * FROM oldimage WHERE oi_archive_name = "";` returns a total of 794 images with this problem. As this is not a high priority task and there is a risk of breaking things, we should do this the next time there is maintenance. The way to fix this is to just remove these entries `DELETE FROM oldimage WHERE oi_archive_name ="";` Prior to doing this, we should take note of one of the affected images, and have a link to the exact contribution that uploaded it. This is to find out if referential integrity breaks or not. We may want to keep a backup of the affected rows afterwards for insurance, if a problem is later discovered. This fix does not delete the actual live files, it merely fixes the cause of why they cannot be deleted.

Soveia added the

bug

Medium

Fire Emblem Wiki

labels 2022-11-21 17:07:42 +00:00

Sign in to join this conversation.