|
В очередной раз поинтересовался как там дела.
Если, коротко : процесс идёт и займёт ещё какое-то время.
Более подробно ниже.
Пришёл такой ответ :
(как и в прошлый раз, только текст без вступительных и завершающих реверансов)
We're still working through the process I'm afraid - we're having to manually update upgrade steps and the database within vB3, partly because of the data being in utf8mb4 format whihc, on older versions of MySQL, is causing issues over field lengths etc.
We're continuing to work on this and will update you as soon as we can.
На что я ответил следующим сообщением :
Yes, back in February, as part of the forum upgrade preparation, I converted the database encoding from "cp1251" to "utf8mb4".
During this process, I encountered (if I understood you correctly) the same issue that you're facing now.
The process was only successful after upgrading MySQL from 5.5.62 to 5.6.51.
This transition caused no issues, and the forum has been running smoothly ever since.
I suspect that vB3 (or the upgrade script) might be using some specific methods that could be causing these problems.
As a possible workaround, you could temporarily convert the database tables to "utf8mb3" and then switch them back to "utf8mb4" at a later upgrade stage.
As I mentioned in the worksheet, I have set up a separate server identical to the production environment.
The forum on this server runs on MySQL 5.6.51.
You're free to use this server as needed — it might help make the upgrade process easier.
|