TYPO3 Core

I see it like this: the changes that are about to me made are shown, the admin should be able to make sense of this. It may well be, that the tables are there, but the extension has long been removed, what then?

If there is really a conflict, the extensions authors should declare this in the dependencies, IMHO.

I agree that conflicts should be stated in the dependencies.

Yet, we cannot solely rely on this as this would require each extension author to know the table changes of each other extension (at least concerning common tables like the static info table).

I opened the bug because of two extensions that conflict in their table definitions although one extension requires the other: static_info_tables and sr_static_info. Each time I update one of them, they offer to update some tables. I've experienced that for one of these extensions, updating the tables breaks yet other extensions, and so I need to remember not to click "Make updates" when updating one of these two extensions.

For all other extensions, using "Make updates" for the tables is required for the update to work.

I don't know exactly how to prevent problems like this, but I don't like how this currently works. This button shouldn't break anything when it usually is required to not break anything.

i can't see a simple solution, extensions may change any field they want, and if they don't know where the conflict happens, they don't use the conflict array.

This should reported to the authors so they can adjust their dependencies.

After thinking about this for a bit, I'm also fine with closing this ticket as "wont't fix".