Opened 3 years ago

Closed 10 months ago

#13346 closed Bug Report - General (Works for me)

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

Reported by: dhighley Owned by:
Priority: major Milestone: unknown
Component: MythTV - General Version: v29.1
Severity: medium Keywords:
Cc: Ticket locked: no


Running of Fedora 29 64 bit. I know nothing about databases and only used with Mythtv.

mythtv-backend-29.1-25.39.20181004git74fff5c285.fc29.x86_64 mariadb-10.3.10-1.fc29.x86_64

mysql_upgrade -p Enter password: Phase 1/7: Checking and upgrading mysql database Processing databases mysql mysql.column_stats OK mysql.columns_priv OK mysql.db OK mysql.event OK mysql.func OK mysql.gtid_slave_pos OK mysql.help_category OK mysql.help_keyword OK mysql.help_relation OK mysql.help_topic OK OK mysql.index_stats OK mysql.innodb_index_stats OK mysql.innodb_table_stats OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.roles_mapping OK mysql.servers OK mysql.table_stats OK mysql.tables_priv OK mysql.time_zone OK mysql.time_zone_leap_second OK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_type OK mysql.user OK Phase 2/7: Installing used storage engines... Skipped Phase 3/7: Fixing views Phase 4/7: Running 'mysql_fix_privilege_tables' ERROR 1071 (42000) at line 646: Specified key was too long; max key length is 1000 bytes FATAL ERROR: Upgrade failed

Change History (1)

comment:1 Changed 10 months ago by Stuart Auchterlonie

Milestone: needs_triageunknown
Resolution: Works for me
Status: newclosed

This error is purely a mysql error, and is not MythTV related.

Closing old tickets

Note: See TracTickets for help on using tickets.