Bug #17856
closed
DB compare fails
0%
Description
many users noticed that EM gives update warning though field definition is equal to existing field. You see it with a "UPDATE NEEDED", eg:
ALTER TABLE fe_groups CHANGE felogin_redirectPid felogin_redirectPid tinytext;
Current value: tinytext
The comparison fails because of missing trim
(issue imported from #M6844)
Files
Updated by Alois Baule over 16 years ago
There's also another error:
DB-Compare complains about a difference between field definition in tables.sql and the real database fields - although they are identical:
e.q. a field definition in tables.sql:
tx_sfadvancedworkspaces_wshighlight_color varchar(30) DEFAULT '' NOT NULL,
The database field is also defined as "NOT NULL", but in the attachment you see the output from DB compare (Screen_Hunter2.jpg).
Updated by Steffen Kamper over 16 years ago
remove NOT NULL from tables.sql and compare works fine.
btw - with attached patch this works fine also with "NOT NULL" in definition.
Updated by Dmitry Dulepov over 16 years ago
Revisions:
TYPO3 4.2: r2796
TYPO3 4.1: r2797