Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
S SobiPro
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Sigsiu.NET GmbH
  • SobiPro
  • Issues
  • #96

Closed
Open
Created May 07, 2018 by Sigrid Suski@TrinitySuOwner

'Specified key was too long; max key length is 767 bytes' on SobiPro installation (some servers only)

https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes

767 bytes is the stated prefix limitation for InnoDB tables in MySQL version 5.6 (and prior versions). It's 1,000 bytes long for MyISAM tables. In MySQL version 5.7 and upwards this limit has been increased to 3072 bytes.

The index limit is 767 bytes, not characters. And since Mysql's utf8mb4 character set (which the rest of the world calls utf8) needs (at most) 4 bytes per character you can only index up to VARCHAR(191)

Assignee
Assign to
1.4.7.2
Milestone
1.4.7.2 (Past due)
Assign milestone
Time tracking

footer

Legal Notice / Impressum | Data Protection / Datenschutzinformation