Steps to replicate the issue (include links if applicable):
What happens?:
Fails with the error:
ERROR: expected column cu_changes.cuc_user_text to exist
This happens because the updates that fail use a method in the PostgresUpdater that requires the fields exist. This means that when the field is later removed the update fails. To fix this the field being present on the DB should be detected first. If the field does not exist then the update does not need to occur.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Don't run postgres updates on specific columns unless the field exists | mediawiki/extensions/CheckUser | master | +41 -18 |
| Status | Subtype | Assigned | Task | |
|---|---|---|---|---|
| · · · | ||||
| Resolved | Zabe | T233004 Update CheckUser for actor and comment table | ||
| Resolved | BUG REPORT | Dreamy_Jazz | T328855 Removal of columns causes 1.39 postgres updates to fail | |
| · · · |
Change 886462 had a related patch set uploaded (by Dreamy Jazz; author: Dreamy Jazz):
[mediawiki/extensions/CheckUser@master] Don't run postgres updates on specific columns unless the field exists
Change 886462 merged by jenkins-bot:
[mediawiki/extensions/CheckUser@master] Don't run postgres updates on specific columns unless the field exists