v 3.20.6 Database update error

kissnavel

Chevereto Member
ALTER TABLE chv_users MODIFY user_username varchar(255) NOT NULL;
ALTER TABLE chv_users MODIFY user_email varchar(255) DEFAULT NULL;
ALTER TABLE chv_users MODIFY user_image_expiration varchar(255) DEFAULT NULL;
ALTER TABLE chv_users MODIFY user_registration_ip varchar(255) NOT NULL;

The following error is reported when updating in the database:
#1071 - Specified key was too long; max key length is 1000 bytes
 

Rodolfo

⭐ Chevereto Godlike
Chevereto Staff
Administrator
Based in the limitation (1000), that's tell me MyIsam table storage engine (Innodb limits to 3072). Most likely you have an old database with MyIsam tables (table storage engine), you should be using innodb with newer releases.

Note that the system won't update the table engine, you must to do that manually.

If that doesn't work you will require to indicate all the context for this, including the version from which you are updating, mysql, engines, etc. I would suggest to actually act and pay atention to the instructions provided by the system, specially the yellow message line that reads "run these queries manually...".
 

kissnavel

Chevereto Member
Based in the limitation (1000), that's tell me MyIsam table storage engine (Innodb limits to 3072). Most likely you have an old database with MyIsam tables (table storage engine), you should be using innodb with newer releases.

Note that the system won't update the table engine, you must to do that manually.

If that doesn't work you will require to indicate all the context for this, including the version from which you are updating, mysql, engines, etc. I would suggest to actually act and pay atention to the instructions provided by the system, specially the yellow message line that reads "run these queries manually...".
When updating from mysql 5.7 to mysql 8.0, the conversion of the database table from the old type to the new type failed but no error was reported.The problem was solved after manual update.
 

Rodolfo

⭐ Chevereto Godlike
Chevereto Staff
Administrator
When updating from mysql 5.7 to mysql 8.0, the conversion of the database table from the old type to the new type failed but no error was reported.The problem was solved after manual update.
Thanks, can you share more details for others having the same problem?
 

kissnavel

Chevereto Member
Thanks, can you share more details for others having the same problem?
When updating from mysql 5.7 to mysql 8.0,most of the database tables are updated from the MyIsam table to the Innodb table,but chv_albums, chv_images, chv_redirects, and chv_users are not updated to the Innodb table.

Before updating v 3.20.6, the other versions update the database without error and the database is running normally.After updating v 3.20.6,chv_albums, chv_images, chv_redirects, and chv_users report errors when updating the database.

After manually updating chv_albums, chv_images, chv_redirects, and chv_users from the MyIsam table to the Innodb table,run SQL query to update the database successfully.
 
Top