-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
"CONVERT TO CHARACTER SET utf8mb4" #15058
Comments
Makeshift: Set the following.
|
Hallo, don't know where to insert these commands. |
You can edit tables structure of Nextcloud database with any database manager (Adminer, phpMYadmin or etc) but firstly you should take a backup of the database. |
Worked, thank you! |
I don't have any database managers on my server, is there a way to fix this via the MySQL console? I'm not sure what sort of query would be used. |
how is this done through the mysql client - so no ssh tunnel is needed to do this on the client |
Or upgrade your MySQL Server to a newer version |
I am on mysql 5.5.62 and an upgrade is not necessary if you configure the innodb stuff the right way as I found out now: Most blog entries to this error suggest to configure But this leads to the mentioned error if you have large datasets as we do. After setting up the Everything regarding tha database migration worked like a charm. |
Can you please provide more step by step on where to change the two settings below? INNODB utf8 VARCHAR(255) I get the following when i run sudo -u www-data php occ maintenance:repair In AbstractMySQLDriver.php line 125: An exception occurred while executing 'ALTER TABLE SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes In PDOStatement.php line 143: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes In PDOStatement.php line 141: SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes |
Looks like updating to the latest version of 10.2 or 10.3 MariaDB from 10.1 will be easier solution update: sudo apt-get install software-properties-common |
Yep, I can also confirm. Please migrate to mariadb as it's actually vastly more supported and documented than mysql and check your Closing as it's irrelevant to nextcloud itself. |
sorry - but nextcloud suggested to do that migration - i won't give a shit to emoji support BUT as nextcloud pointed me to do so i did and ran into that problem. I would suggest to check the innodb_large_prefix=1 status during the upgrade preparation tests... |
15.0.7 --> 16.0.1 |
Just use in the mysql cli. But probably the best thing would be to change the MYSQL config, with this:
|
Thanks a lot Antonio! It helped me a lot - an additional problem for me is, that I'm working in docker... For me, the change to the MySQL config had to be:
Maybe it depends on the MySQL/MariaDB-version. Mine is:
If anybody else has this problem with Docker (specifically linuxserver/nextcloud & linuxserver/mariadb):
Back to nextcloud:
|
No problem glad that I could help 👍 , yeah probably it depends by the mariadb version used. If you use the linuxserver/mariadb docker's container, you could just change the config The mysql service will reload with the container :) |
How will i do this via mysql console? |
Hello, I have no access to the conf file and no way to to modify it. I first have the following error So I applied :
Then I launch the update again and now the error is:
I am now stuck with this bug and don't know what to do because when I look at the table I don't know which field has to be promoted to VARCHAR(191) Anyone can help ? |
Hi,
I encountered an error while updating the database:
Doctrine\DBAL\Exception\DriverException: An exception occurred while executing 'ALTER TABLE
oc_addressbooksCONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_bin;': SQLSTATE[42000]: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes
How can I fix this?
PHP 7.2
Nextcloud V: 16 Beta 3 -> 16 RC1
The text was updated successfully, but these errors were encountered: