Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mariadb-10.1 mariadb-10.1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • Olaf van der Spek
  • mariadb-10.1mariadb-10.1
  • Repository
Switch branch/tag
  • mariadb-10.1
  • debian
  • additions
  • mariadb.conf.d
  • 50-server.cnf
Find file BlameHistoryPermalink
  • Otto Kekäläinen's avatar
    Fix 'max key length is 767 bytes' errors (Closes: #886756) · 89ae638d
    Otto Kekäläinen authored Aug 07, 2018
    Allow index keys up to 3072 bytes. Many apps expect VARCAHR(255) to work.
    Since we introduced UTF-8, that has not been the case. This can be fixed
    via option 'innodb_default_row_format' that was backported to 10.0.x
    series recently.
    
    The option 'innodb_file_per_table' is 'on' by defautl since MariaDB 5.5,
    so there is no need to define it.
    
    See also
    https://jira.mariadb.org/browse/MDEV-14904
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848603
    https://mariadb.com/kb/en/library/xtradbinnodb-server-system-variables/#innodb_file_format
    89ae638d