blocks|key|2909890|text|在BK435给出的答案的帮助下，我做了以下工作并解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2909891|set+global+innodb_file_format+=+BARRACUDA;
set+global+innodb_large_prefix+=+ON;
create+table+test+(........)+ENGINE=InnoDB+DEFAULT+CHARSET=utf8+ROW_FORMAT=DYNAMIC;|code-block|syntax|javascript|2909892|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

With the help of the answer given by BK435, I did the following and solved the problem.

<pre><code>set global innodb_file_format = BARRACUDA;
set global innodb_large_prefix = ON;
create table test (........) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=DYNAMIC;
</code></pre>

blocks|key|2697753|text|您尝试为其编制索引的列太大，并且您的设置对于innodb_large_prefix而言一定不正确。为了让innodb_large_prefix正常工作，还必须设置一些prerequisites参数。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2697754|您可以通过运行以下命令进行检查，以确保设置了innodb_large_prefix：|2697755|show+global+variables+like+'innodb_lar%25';|2697756|以下是使用innodb_large_prefix的几个先决条件：|2697757|您需要设置全局变量innodb_file_format=BARRACUDA|2697758|要检查设置，请运行：show+global+variables+like+'innodb_fil%25';|2697759|在表级，您必须使用ROW_FORMAT=DYNAMIC或ROW_FORMAT=COMPRESSED|2697760|对于Innodb，默认情况下以紧凑格式(ROW_FORMAT=COMPACT)存储行。|2697761|entityMap|0|LINK|mutability|MUTABLE|url|http://mechanics.flite.com/blog/2014/07/29/using-innodb-large-prefix-to-avoid-error-1071/|1|https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html|2|https://dev.mysql.com/doc/refman/5.6/en/glossary.html#glos_barracuda|3|https://dev.mysql.com/doc/refman/5.6/en/innodb-row-format-specification.html^0|M|J|1G|J|2B|D|0|0|M|J|1|0|0|15|0|0|S|9|2|0|A|15|0|0|2|6|3|0^^$0|@$1|2|3|4|5|6|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|F|3|G|5|6|7|1F|8|@]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|H|3|I|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1M|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1N|8|@]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|N|3|O|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1U|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1V|8|@]|D|@$9|1W|A|1X|1|1Y]]|E|$]]|$1|T|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10]]|11|$5|W|X|Y|E|$Z|12]]|13|$5|W|X|Y|E|$Z|14]]|15|$5|W|X|Y|E|$Z|16]]]]

Your column that you are trying to index is too large and your settings must not be correct for <code>innodb_large_prefix</code>. There are a couple <a href="http://mechanics.flite.com/blog/2014/07/29/using-innodb-large-prefix-to-avoid-error-1071/" rel="noreferrer">prerequisites</a> parameters that also have to be set in order for <code>innodb_large_prefix</code> to work correctly.

You can check to make sure that <a href="https://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html" rel="noreferrer">innodb_large_prefix</a> is set by running:

<code>show global variables like 'innodb_lar%';</code>

Here are a couple prerequisites for using innodb_large_prefix:

You need to set your global variable innodb_file_format=<a href="https://dev.mysql.com/doc/refman/5.6/en/glossary.html#glos_barracuda" rel="noreferrer">BARRACUDA</a>

to check settings run: <code>show global variables like 'innodb_fil%';</code>

At the table level you have to use ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED

for <a href="https://dev.mysql.com/doc/refman/5.6/en/innodb-row-format-specification.html" rel="noreferrer">Innodb</a>, rows are stored in COMPACT format (ROW_FORMAT=COMPACT) by default.

blocks|key|2698509|text|从Wamp版本3.2.6开始|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698510|只需编辑此文件：C:\wamp64\bin\mysql\mysql8.0.27\my.ini更改innodb-default-row-format值的配置|offset|length|style|BOLD|CODE|2698511|来自innodb-default-row-format=compact|2698512|转到innodb-default-row-format=dynamic|2698513|重启mysql|2698514|entityMap^0|0|8|12|1C|P|0|2|X|0|2|X|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@$D|X|E|Y|F|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|Z|8|@$D|10|E|11|F|H]]|9|@]|A|$]]|$1|M|3|N|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$]]

From Wamp Version 3.2.6 
Just edit this file:
C:\wamp64\bin\mysql\mysql8.0.27\my.ini
Change the config for <code>innodb-default-row-format</code> value 
from <code>innodb-default-row-format=compact</code> 
to <code>innodb-default-row-format=dynamic</code> 
Restart mysql

blocks|key|2910378|text|我使用的是MariaDB版本10.1.38，并使用了下面所有给定的命令，但它不起作用-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2910379|set+global+innodb_large_prefix+=+ON;
Query+OK,+0+rows+affected+(0.00+sec)

set+global+innodb_file_per_table+=+ON;
Query+OK,+0+rows+affected+(0.00+sec)

set+global+innodb_file_format+=+Barracuda;
Query+OK,+0+rows+affected+(0.00+sec)

SET+GLOBAL+innodb_default_row_format+=+'DYNAMIC';|code-block|syntax|javascript|2910380|因为在重新启动MySQL+(或MariaDB)后，在mysql提示符下使用以下命令将不会反映这些设置:显示变量，如'innodb%25'；|2910381|然后我编辑了My.ini并将这些设置添加到位于以下位置的文件中-+C:\xampp\mysql\bin\my.ini|offset|length|style|BOLD|2910382|##+Innodb+settings+to+bypass+error+of+max+size+737
innodb-file-format=barracuda
innodb-file-per-table=ON
innodb-large-prefix=ON
##+Above+3+didnot+work+so+i+added+below
innodb_default_row_format+=+'DYNAMIC'|2910383|来源：https://www.experts-exchange.com/questions/28675824/Why-am-I-unable-to-turn-innodb-large-prefix-ON-successfully-Every-time-I-reboot-mySql-on-my-Ubuntu-VPS-it-resets-to-OFF.html|2910384|entityMap|0|LINK|mutability|MUTABLE|url|https://www.experts-exchange.com/questions/28675824/Why-am-I-unable-to-turn-innodb-large-prefix-ON-successfully-Every-time-I-reboot-mySql-on-my-Ubuntu-VPS-it-resets-to-OFF.html^0|0|0|0|0|1M|0|0|3|4W|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@$K|14|L|15|M|N]]|9|@]|A|$]]|$1|O|3|P|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|17|8|@]|9|@$K|18|L|19|1|1A]]|A|$]]|$1|S|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I was using MariaDB version 10.1.38 and used all of the below given commands but it did not work -

<pre><code>set global innodb_large_prefix = ON;
Query OK, 0 rows affected (0.00 sec)

set global innodb_file_per_table = ON;
Query OK, 0 rows affected (0.00 sec)

set global innodb_file_format = Barracuda;
Query OK, 0 rows affected (0.00 sec)

SET GLOBAL innodb_default_row_format = 'DYNAMIC';
</code></pre>

Because after you restart your MySQL (or MariaDB), these settings will not reflect back using the command at the mysql prompt: show variables like 'innodb%';

Then I edited My.ini and added these settings in the file at below location-
C:\xampp\mysql\bin\my.ini

<pre><code>## Innodb settings to bypass error of max size 737
innodb-file-format=barracuda
innodb-file-per-table=ON
innodb-large-prefix=ON
## Above 3 didnot work so i added below
innodb_default_row_format = 'DYNAMIC'
</code></pre>

source:<a href="https://www.experts-exchange.com/questions/28675824/Why-am-I-unable-to-turn-innodb-large-prefix-ON-successfully-Every-time-I-reboot-mySql-on-my-Ubuntu-VPS-it-resets-to-OFF.html" rel="noreferrer">https://www.experts-exchange.com/questions/28675824/Why-am-I-unable-to-turn-innodb-large-prefix-ON-successfully-Every-time-I-reboot-mySql-on-my-Ubuntu-VPS-it-resets-to-OFF.html</a>

blocks|key|134496|text|对于我使用的Mariadb+10.1.31，只需在登录Mysql+CLI时添加以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|134497|SET+GLOBAL+innodb_file_format+=+Barracuda;

SET+GLOBAL+innodb_file_per_table+=+ON;

SET+GLOBAL+innodb_large_prefix+=+ON;

SET+GLOBAL+innodb_default_row_format+=+'DYNAMIC';|code-block|syntax|javascript|134498|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For me using Mariadb 10.1.31, just add this while you login in Mysql CLI:

<pre><code>SET GLOBAL innodb_file_format = Barracuda;

SET GLOBAL innodb_file_per_table = ON;

SET GLOBAL innodb_large_prefix = ON;

SET GLOBAL innodb_default_row_format = 'DYNAMIC';
</code></pre>

blocks|key|2697955|text|只需将以下选项添加到my.cnf|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2697956|[mysqld]
innodb_file_format=Barracuda
innodb_file_per_table=1
innodb_large_prefix=1|code-block|syntax|javascript|2697957|然后，重启mysql服务器，问题就解决了。|2697958|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Just add the following options to my.cnf

<pre><code>[mysqld]
innodb_file_format=Barracuda
innodb_file_per_table=1
innodb_large_prefix=1
</code></pre>

Then, restart mysql server the problem will be resolved.

blocks|key|131813|text|尽管正确地配置了innodb_large_prefix，我还是遇到了同样的错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|131814|此问题出现在已使用的排序规则中。我的数据库将默认排序规则设置为utf8mb4_bin+(您可以在数据库的phpmyadmin“操作”选项卡中查看它)。这意味着它每个字符使用4个字节，而utf8排序规则(例如utf8_unicode_ci)每个字符使用3个字节。|131815|在这种情况下，您可以使用不同的排序规则，例如，通过在CREATE+TABLE语句的末尾添加DEFAULT+CHARSET=utf8，或者通过仅使用列值的一部分来限制索引大小，如KEY+'identifier'+(column1(5),column2(10))。|131816|另请参阅相关问题：#1071+-+Specified+key+was+too+long;+max+key+length+is+767+bytes|131817|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes^0|8|J|0|V|B|0|Q|C|19|K|2G|15|0|9|1R|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|16|8|@]|D|@$9|17|A|18|1|19]]|E|$]]|$1|L|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

I had the same error despite having <code>innodb_large_prefix</code> configured correctly.

The issue was in used collation. My db had default collation set to <code>utf8mb4_bin</code> (you can check it in phpmyadmin "Operations" tab for database). It means it uses 4 bytes per char, while utf8 collation (e.g. utf8_unicode_ci) uses 3 bytes per char.

in this case you can either use different collation e.g. by adding <code>DEFAULT CHARSET=utf8</code> at the end of the <code>CREATE TABLE</code> statement, or limit the index size by using just a part of the column value 
like <code>KEY 'identifier' (column1(5),column2(10))</code>.

See also related question: <a href="https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes">#1071 - Specified key was too long; max key length is 767 bytes</a>

blocks|key|2698178|text|在我的例子(MySQL版本5.6)中，问题是我试图创建一个包含最多256个字符的列的表(数据库使用utf8排序规则)，因此每1个utf8字符3个字节=+256*3=768个字节。修复方法是简单地使用255个字符，而不是256个。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698179|我也可以像其他人建议的那样设置innodb_large_prefix，但在我的例子中，只有更少的符号会更容易。|2698180|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my case (MySQL version 5.6) the issue was that I was trying to create a table with a column that can have up to 256 characters (the db uses utf8 collation), so 3 bytes per 1 utf8 character = 256*3=768 bytes. The fix was to simply have 255 characters instead of 256. 

I could also set innodb_large_prefix, like others suggest, but in my case it was easier to just have fewer symbols.

blocks|key|131993|text|正如@sasank-mukkamala所说，对我来说，只有添加ROW_FORMAT=DYNAMIC来创建命令才是正确的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|131994|create+table+`NameOfTheTable`+(........)+ENGINE=InnoDB+DEFAULT+CHARSET=utf8mb4+ROW_FORMAT=DYNAMIC;|code-block|syntax|javascript|131995|entityMap^0|V|I|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Just like @sasank-mukkamala said , for me only adding <code>ROW_FORMAT=DYNAMIC</code> to create command did it rightly.
<pre><code>create table `NameOfTheTable` (........) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 ROW_FORMAT=DYNAMIC;
</code></pre>

blocks|key|2698545|text|即时通信使用Mysql+5.7|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698546|点击PHPMyAdmin+(主页)点击Variables+On+innodb+default+row+formart，点击edit然后输入2，然后点击save，系统会再次将变量值显示为动态导入表|2698547|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Im using Mysql 5.7
Click PHPMyAdmin (home)
Click Variables
On innodb default row formart, click edit then enter 2, then click save
It will show variable value as dynamic
Import table again

blocks|key|2698326|text|我遇到这个问题是因为我试图用varchar(254)创建一个字符串主键。有时很容易被忽视..因此，还要仔细检查索引类型和长度:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698327|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had this problem because I tried to create a String primary key with varchar(254). Easy to overlook sometimes.. So double check your index type and length as well :)

blocks|key|2698473|text|如果有人正在使用MySQL+5.6，我找到的唯一解决方案是更新到MySQL+5.7并设置my.cnf，如前面的评论(https://stackoverflow.com/a/57465002/2300390)所述。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2698474|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/57465002/2300390^0|18|6|1M|18|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

In case someone is working with MySQL 5.6 the only solution that I found was to update to MySQL 5.7 and setting <code>my.cnf</code> as mentioned in previous comments (<a href="https://stackoverflow.com/a/57465002/2300390">https://stackoverflow.com/a/57465002/2300390</a>).

blocks|key|2698597|text|这对我很有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2698598|从Wamp版本3.2.6开始|2698599|只需编辑此文件:+C:\wamp64\bin\mysql\mysql8.0.27\my.ini|2698600|更改innodb-default-row-format的配置值|offset|length|style|CODE|2698601|来自innodb-default-row-format=compact|2698602|转到innodb-default-row-format=dynamic|2698603|重启mysql|2698604|entityMap^0|0|0|0|2|P|0|2|X|0|2|X|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@$H|X|I|Y|J|K]]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@$H|10|I|11|J|K]]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@$H|13|I|14|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|15|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|S|$]]

This worked for me:
From Wamp Version 3.2.6 
Just edit this file: C:\wamp64\bin\mysql\mysql8.0.27\my.ini 
Change the config for <code>innodb-default-row-format</code> value 
from <code>innodb-default-row-format=compact</code> 
to <code>innodb-default-row-format=dynamic</code> 
Restart mysql

blocks|key|2697832|text|我有相同的错误，但在不同的问题上。我在导入数据(数据和模式)脚本时遇到此错误。删除唯一索引为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2697833|答案来自this+link|offset|length|2697834|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/24853828/index-column-size-too-large-the-maximum-column-size-is-767-bytes-for-int-dat^0|0|4|9|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I had the same error but on a different issue. I got this error while importing a data (data and schema) script. Deleting the Unique Index fixed the issue for me.

Answer taken from <a href="https://stackoverflow.com/questions/24853828/index-column-size-too-large-the-maximum-column-size-is-767-bytes-for-int-dat">this link</a>

blocks|key|2697802|text|设置以下系统变量：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2697803|innodb_buffer_pool_size....................................+702545920
innodb_file_format.........................................+Barracuda
innodb_file_format_check...................................+ON
innodb_file_format_max.....................................+Barracuda
innodb_file_per_table......................................+ON
innodb_large_prefix........................................+ON
innodb_log_file_size.......................................+50331648|code-block|syntax|javascript|2697804|此外，请确保在创建模式时将其创建为Latin1。这就是最终解决我的问题的原因。|offset|length|style|BOLD|2697805|entityMap^0|0|0|H|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Set the below system variables:

<pre><code>innodb_buffer_pool_size.................................... 702545920
innodb_file_format......................................... Barracuda
innodb_file_format_check................................... ON
innodb_file_format_max..................................... Barracuda
innodb_file_per_table...................................... ON
innodb_large_prefix........................................ ON
innodb_log_file_size....................................... 50331648
</code></pre>

Also, make sure when you create your schema you create it as Latin1. That is what finally fixed me.

When I run a program which does something with MySQL, I got this error message:

<blockquote>
 2015-06-10 15:41:12,250 ERROR app.wsutils 419 INCRON: Error: ('HY000',
 '[HY000] [MySQL][ODBC 5.2(w) Driver][mysqld-5.7.7-rc-log]Index column
 size too large. The maximum column size is 767 bytes. (1709)
 (SQLExecDirectW)')
</blockquote>

I Googled a little bit, and found this error might be relating to the <code>innodb_large_prefix</code> option. However, I am using MySQL 5.7.7 rc, which has already set <code>innodb_large_prefix</code> to be "ON" (checked in MySQL Workbench), allowing up to 3072 bytes. I am not sure if that is the problem with <code>innodb_large_prefix</code> or not.

Anyway, does anyone have an idea how to fix this problem?

MySQL error: The maximum column size is 767 bytes

数据库

服务器

MariaDB

MySQL

当我运行一个用MySQL做某些事情的程序时，我得到了这个错误消息： 2015-06-10 15:41:12,250 ERROR app.wsutils 419 INCRON: Error：('HY000'，'HY000ODBC 5.2(w) DriverIndex列大小太大。最大列大小为767字节。(1709) (SQLExecDirectW)')我用谷歌搜索了一下，发现这个错误可能与innodb

问MySQL错误:最大列大小为767字节
EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL错误:最大列大小为767字节EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MySQL错误:最大列大小为767字节
EN