Wiki

User Tools

Site Tools

Trace: • add_route • configure_banners
mysql:error_1071

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
mysql:error_1071 [2016/07/01 23:15] – petermysql:error_1071 [2020/07/15 09:30] (current) – external edit 127.0.0.1
Line 8: Line 8:
 Thus, you need to multiply your key field's character limit by, 1, 3, or 4 (depending on which character set is being used) to determine the number of bytes the key field will actually try to use.   Thus, you need to multiply your key field's character limit by, 1, 3, or 4 (depending on which character set is being used) to determine the number of bytes the key field will actually try to use.  
  
-  * For **uft8** a maximum of 255 characters can therefore be used for InnoDB key field because 767/3≈255. +  * For **uft8** a maximum of 255 characters can therefore be used for an InnoDB key field because 767/3≈255. 
-  * For **uft8mb4** a maximum of 191 characters can therefore be used for InnoDB key field because 767/4≈191.+  * For **uft8mb4** a maximum of 191 characters can therefore be used for an InnoDB key field because 767/4≈191.
  
 There is also a separate 3072 byte limit per index.  The 767 byte limit is per column, so you can include multiple columns (each 767 bytes or smaller) up to 3072 total bytes per index, but no column longer than 767 bytes.  (MyISAM is a little different.  It has a 1000 byte index length limit, but no separate column length limit within that). There is also a separate 3072 byte limit per index.  The 767 byte limit is per column, so you can include multiple columns (each 767 bytes or smaller) up to 3072 total bytes per index, but no column longer than 767 bytes.  (MyISAM is a little different.  It has a 1000 byte index length limit, but no separate column length limit within that).
  
  
-One workaround for these limits is to only index a prefix, for example, here only the 191 characters from column1 is part of the index:+One workaround for these limits is to only index part of a field, for example, here only 191 characters from column1 is part of the index:
  
 <code mysql> <code mysql>
Line 30: Line 30:
 </code> </code>
  
-Read on for details and examples about **innodb_large_prefix**.+ 
 +===== Using innodb_large_prefix =====
  
 Here are a few pre-requisites for using **innodb_large_prefix**: Here are a few pre-requisites for using **innodb_large_prefix**:
Line 39: Line 40:
 The default file format is still Antelope for backwards compatibility, and the default row format is COMPACT. The default file format is still Antelope for backwards compatibility, and the default row format is COMPACT.
  
-You can set both **innodb_file_format** and **innodb_large_prefix** dynamically, but you should also set them in my.cnf so they survive a restart.+You can set both **innodb_file_format** and **innodb_large_prefix** dynamically, but you should also set them in **my.cnf** so they survive a restart.
  
 Here’s an example.  If I try to create this table with **innodb_large_prefix** disabled I get an error: Here’s an example.  If I try to create this table with **innodb_large_prefix** disabled I get an error:
mysql/error_1071.1467414925.txt.gz · Last modified: 2020/07/15 09:30 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki