Bug #86793
closed
Renamed columns are not correctly detected by database schema diff
Added by Helmut Hummel over 5 years ago.
Updated almost 5 years ago.
Description
When using the default collation utf8mb4, renamed columns are not detected any more.
When you set up a new TYPO3 9.5 instance with MySQL
And rename one filed in any extensions ext_tables.sql file
I would expect to see the old field name offered to be dropped and a new field offered to be created with a new field name
What actually happens is, that database schema update does not show any changes.
Same is true for renaming an index.
- Related to Feature #80398: Make default charset and collation for new tables configurable added
confirmed. seen that, too. we had a fix related to this back in v8 times and should pick up some details from there. if that is related to utf8mb4, it's the explanation we did not see that earlier.
- Status changed from New to Under Review
Christian Kuhn wrote:
confirmed. seen that, too. we had a fix related to this back in v8 times and should pick up some details from there. if that is related to utf8mb4, it's the explanation we did not see that earlier.
Would be helpful, if you could pick up the change request or ticket from back then. I didn't find anything.
otoh I'm now pretty convinced, that I found a proper fix for that.
Code was broken since 8, but was issue was leveraged with utf8mb4 transition changes.
So maybe the fix is worth backporting to 8 although the error is not that easy to trigger (if at all for column renames)
- Related to Bug #78771: ConnectionMigrator does not handle renamed columns added
- Related to Bug #81756: DatabaseSchemaComparator does not handle renamed columns added
Thanks, the related tickets and change requests helped
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by