可能重复:
请查看此表格:
www.mediawiki/wiki/Manual:Logging_table
正如你可以看到wikipedia使用varbinary而不是varchar:
| log_type | ** varbinary **(32)| NO | MUL | | | log_action | ** varbinary **(32)| NO | | | | log_timestamp | ** binary **(14)| NO | MUL | 19700101000000 | | log_user | int(10)unsigned | NO | MUL | 0 | | log_user_text | ** varbinary **(255)| | | |所有这些信息都是文本,所以为什么将它们保存为二进制? $ b 解决方案Mediawiki已从varchar更改为varbinary href =svn.wikimedia/viewvc/mediawiki?view=revision&revision=80547> 2011年初:
War on varchar。将所有出现的varchar(N)和varchar(N)二进制更改为varbinary(N)。 varchars在带有某些配置的MySQL数据库上导致问题( collations错误的混合),大多数特别是默认的MySQL配置。
Possible Duplicate: What is the advantage of using varbinary over varchar here?
Please take a look at this table :
www.mediawiki/wiki/Manual:Logging_table
As you can see wikipedia use varbinary instead of varchar :
| log_type | **varbinary**(32) | NO | MUL | | | log_action | **varbinary**(32) | NO | | | | log_timestamp | **binary**(14) | NO | MUL | 19700101000000 | | log_user | int(10) unsigned | NO | MUL | 0 | | log_user_text | **varbinary**(255) | | | |All of these information are text , so why they save them as binary ?
They do this for all tables .
解决方案Mediawiki changed from varchar to varbinary in early 2011:
War on varchar. Changed all occurrences of varchar(N) and varchar(N) binary to varbinary(N). varchars cause problems ("Invalid mix of collations" errors) on MySQL databases with certain configs, most notably the default MySQL config.
更多推荐
为什么varbinary而不是varchar
发布评论