Wondering if this will always be free?  See why free is better.

Main Menu

Does SMF 2.0.17 work with MySQL version 8.0?

Started by Wolpo, June 08, 2020, 02:19:48 PM

Previous topic - Next topic



can anybody tell me whether MySQL 8.0 is compatible to SMF 2.0.17?

(My provider will upgrade their MySQL from version 5.6.29 to version 8.0.19.)

Here's a list of what has been removed in MySQL 8.0:

Thank you!


It hasn't been tested to any significant degree.

I would expect the answer to be 'will have some issues' because it isn't just about 'what has been removed' but what has also changed. There are still some issues from 5.7's strict mode changes being worked out.

That said, the in-development 2.1 is known to be better on MySQL 8.


If you do end up using it with MySQL 8 please do let us know the results.


I've done some preliminary testing...  Utf8 SMF DBs seem to work ok.  Non-utf8 implementations definitely have issues (e.g., errno 1071s).  Don't even try it if not converted to utf8 yet.

Sql_mode needs attention. 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp


Good to know, thanks. Did your testing include posting, attachments, searches and maintenance routines?


It was not thorough.  Installs & upgrades (various settings), posting & attachments, yes, but not much beyond that.
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp


Thanks. I will report my observations after 18 June 2020.


The update will happen a bit later. I'll report my results after 3 July 2020.


Just got a message from my provider; they won't update to MySQL 8.0.19.



"In our original planning it was intended to upgrade MySQL to version MySQL 8.0.19. However, after the conversion of the first systems, we observed some issues with the new MySQL version in live operation, which were confirmed by feedback from our customers. In the meantime we could verify that a bug in MySQL 8.0.19 can significantly affect the system load in certain constellations, which we unfortunately could not detect in our previous tests. For this reason, we have decided to use MySQL Version 5.7 for all pending migrations. We will update to MySQL 8 at a later date after the bug has been fixed."