• 🤗 This support section is delivered by the community, by other users of the software. Support in this section is not delivered by Chevereto Staff, remarks and issues in this section should be always taken with the appropriate context and care, with a grain of salt.

Specified key was too long; max key length is 767 bytes

Logan

Chevereto Member
Hi
I have updated my chevereto to version 3.20.1.
My server has MySQL 5.6.44 and PHP 7.3.24 with NGINX.
After the upgrade, it shows me some errors and to update SQL query to MySQL.
all queries had applied, even to Trunch table chv_assets.
But after that, i am unable to run CRERE TABLE chv_assets on SQL Query
CREATE TABLE chv_assets (
asset_id bigint(32) NOT NULL AUTO_INCREMENT,
asset_key varchar(255) NOT NULL,
asset_md5 varchar(32) NOT NULL,
asset_filename varchar(255) NOT NULL,
asset_file_path varchar(255) NOT NULL,
asset_blob blob,
PRIMARY KEY (asset_id),
UNIQUE KEY key (asset_key) USING BTREE,
KEY md5 (asset_md5),
KEY filename (asset_filename),
KEY file_path (asset_file_path)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;


I am seeing this error


Code:
[HEADING=2]Error[/HEADING]
SQL query: Copy

CREATE TABLE `chv_assets` (
 `asset_id` bigint(32) NOT NULL AUTO_INCREMENT,
 `asset_key` varchar(255) NOT NULL,
 `asset_md5` varchar(32) NOT NULL,
 `asset_filename` varchar(255) NOT NULL,
 `asset_file_path` varchar(255) NOT NULL,
 `asset_blob` blob,
 PRIMARY KEY (`asset_id`),
 UNIQUE KEY `key` (`asset_key`) USING BTREE,
 KEY `md5` (`asset_md5`),
 KEY `filename` (`asset_filename`),
 KEY `file_path` (`asset_file_path`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4

MySQL said:

#1071 - Specified key was too long; max key length is 767 bytes

Please Help..
Thanks
 
Top