Bug #104449
closedDrop fields are not executed in Database Analyzer
100%
Description
After upgrading an instance from 11.5 to 12.4 (using version 12.4.17), I cannot get rid of a few Database Analyzer removed fields (see screenshot). Each time I apply the selected changes, the notification says in green it's successful, but the fields appear again:
If I execute these two drop/rename fields from mysql console or phpmyadmin and I "Run database compare again", then two more differences appear:
```
ALTER TABLE `sys_category` DROP `zzz_deleted_cruser_id`;
ALTER TABLE `sys_file_collection` CHANGE `cruser_id` `zzz_deleted_cruser_id` INT UNSIGNED DEFAULT 0 NOT NULL;
```
If I execute them in mysql console, other two appear:
```
ALTER TABLE `sys_file_collection` DROP `zzz_deleted_cruser_id`;
ALTER TABLE `sys_file_reference` CHANGE `cruser_id` `zzz_deleted_cruser_id` INT UNSIGNED DEFAULT 0 NOT NULL;
```
and so on...
All of them seem related to `cruser_id` removed field;
Files
Updated by Stefan Bürk 5 days ago
- Category set to Database API (Doctrine DBAL)
- Assignee set to Stefan Bürk
Updated by Eric Harrer 5 days ago
I can confirm this behaviour. After I downgraded to TYPO3 12.4.16, all suggested changes of the analyser could be applied again.
Updated by Stefan Bürk 5 days ago
- Related to Bug #93223: Wrong syntax for ALTER INDEX on PostgreSQL added
Updated by Gerrit Code Review 2 days ago
- Status changed from Accepted to Under Review
Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85379
Updated by Gerrit Code Review 2 days ago
Patch set 2 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/85379
Updated by Stefan Bürk 2 days ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 054e4b90ed1fc002fef72d32cb40e33b27b6560b.