Specified key was too long during installation

With a database configured as utf8mb4, installation fails with the message "Specified key was too long". Maximum is 1000. This may happen because the database will assume each character can take 4 bytes, and there is an index that contains character string(s) that take the total above 1000. What can be done?

Be sure to be using InnoDB engine and ensure InnoDB is configured with innodb_large_prefix enabled. You should have no issues with CB or Joomla indexes at that point.

Thanks. I am working with data from an old site. I have converted all the tables from MyISAM to InnoDB and configured the database server with innodb_large_prefix = 1 and restarted. All the conversions succeeded. But installing the latest Community Builder gives a failure, with message:

Index column size too large. The maximum column size is 767 bytes.

Ensure your tables also have ROW_FORMAT set to DYNAMIC. Example as follows.


This all should've been upgraded by Joomla of which CB would upgrade to as well since CB matches Joomlas usage.

If the above doesn't work as "Index column size too large. The maximum column size is 767 bytes." is the limit without innodb_large_prefix being enabled then you likely don't have innodb_file_format set to BARRACUDA, which is also necessary.

Thanks. I have changed the database server my.cnf to set innodb_file_format = Barracuda, and restarted. Have checked that the running database server has innodb_file_format set correctly, and also that it has innodb_large_prefix set on. I've gone through all the jos_comprofiler tables running the command "ALTER TABLE table_name_here ROW_FORMAT=DYNAMIC;". shows the error .

Sample table looks like this in phpMyAdmin:

Your ROW_FORMAT is set to COMPACT and not DYNAMIC. Suggest contacting your host if still having issues configuring InnoDB. See the below for additional information.

stackoverflow.com/questions/30761867/mysql-error-the-maximum-column-size-is-767-bytes