-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade failed from 1.11.4 to 1.12.4 on MySQL with Error 1118: Row size too large... #12777
Comments
This is a duplicate of #12258, which is a duplicate of #11990 which was a duplicate of #11984 which itself is a duplicate of #9347. Gitea is very clearly telling you what the problem is: In fact it tells you no less than ten times:
Have you tried |
@zeripath, I've tried gitea convert, and it's done without error, and I could not find the table/column information which we need to change to Text/BloBs... |
Has gitea convert run successfully? You may need to run it a few times. See: https://docs.gitea.io/en-us/faq/#upgrade-errors-with-mysql |
it seemed that convert works fine. but migrate throws exception.
|
@w6m6 did you change your config file too? (utf8mb4) |
@6543 we r using mariadb 15.1, and added the config item in server.cnf From gitea server, we get the information as below: [root@KSSHUAT01618 bin]# mysql -u gitea -h 172.25.223.42 -p Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show variables like 'char%'; |
thanks for diging int this problem - convert should take care of it ... -> #12801 |
Description
When we upgrade the existing gitea from 1.11.4 to 1.12.4, a error message were thrown and attached as below.
[x]
):The text was updated successfully, but these errors were encountered: