| 1 | -- Issues became work items of the workspace (g1t #57). What g1t opened |
| 2 | -- for an upgrade, and what it was put on to fix an alert, is now a work |
| 3 | -- item, by its number in the repository's workspace. |
| 4 | -- |
| 5 | -- Until the work service has numbered the moved issues, these columns |
| 6 | -- still hold the old issue numbers of each row's repository: `work.migrated` |
| 7 | -- rewrites them (lib.rs `work_migrated`). Every new number in a workspace |
| 8 | -- is above every old number of its repositories, so a rewritten value is |
| 9 | -- never taken for an old one. |
| 10 | ALTER TABLE updates RENAME COLUMN issue TO item; |
| 11 | ALTER TABLE update_pulls RENAME COLUMN issue TO item; |
| 12 | ALTER TABLE code_alerts RENAME COLUMN issue TO item; |
| 13 | ALTER TABLE alert_fixes RENAME COLUMN issue TO item; |
| 14 | ALTER TABLE upgrades RENAME COLUMN number TO item; |