Check Charset - Database validity, when you do the one the other has a problem and vise versa... #6091
Replies: 1 comment 3 replies
|
Hoi @Alex-e107nl, your title had it right: the two tools want different things, and the one that was wrong is Check database validity. Deltik asked me to fix it before asking you anything, and the fix is up as #6092. What happened on your site. Check database validity had decided your server caps InnoDB indexes at 767 bytes. That would make a 255-character key too wide for utf8mb4, so it wanted the eight tables that carry such a key ( The 767 was a misreading. It asks the server for Two things worth knowing about your database as it stands.
After the fix, a conversion that would lose data fails with the server's error in the log instead of quietly writing |

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
@e107help oke, did a update with github 25-08-2026 and all updates went fine but, there is still a problem with the database tables, as far as i know they all should be utf8mb4_general_ci
Check charset:
When i Convert the tables i get the message:
Error
ALTER TABLE
e107_downloadMODIFY download_name varbinary(255);ALTER TABLE
e107_downloadMODIFY download_url varbinary(255);ALTER TABLE
e107_downloadMODIFY download_author varbinary(100);ALTER TABLE
e107_downloadMODIFY download_author_website varbinary(200);ALTER TABLE
e107_newsMODIFY news_title varbinary(255);ALTER TABLE
e107_newsMODIFY news_meta_keywords varbinary(255);ALTER TABLE
e107_downloadMODIFY download_description blob;ALTER TABLE
e107_newsMODIFY news_body longblob;ALTER TABLE
e107_newsMODIFY news_extended longblob;ALTER TABLE
e107_newsMODIFY news_meta_description blob;ALTER TABLE
e107_newsMODIFY news_summary blob;So tried Check database validity:
Got the message Success
Tables appear to be okay!
But then in check charset the same error is there again... so somewhere something is not configured right?
All reactions