[Reproduction] Introduction to MySQL collation

Original address, http://www.mysqltutorial.org/mysql-collation/

 

Introduction to MySQL collation

A MySQL collation is a set of rules used to compare characters in a particular character set. Each character set in MySQL can have more than one collation, and has, at least, one default collation. Two character sets cannot have the same collation.

MySQL provides you with the SHOW CHARACTER SET  statement that allows you to get the default collations of character sets as follows:

1

SHOW CHARACTER SET;

MySQL character sets

The values of the default collation column specify the default collations for the character sets.

By convention, a collation for a character set begins with the character set name and ends with _ci (case insensitive) _cs  (case sensitive) or _bin  (binary).

To get all collations for a given character set, you use the SHOW COLLATION  statement as follows:

1

SHOW COLLATION LIKE 'character_set_name%';

For example, to get all collations for the latin1 character set, you use the following statement:

1

SHOW COLLATION LIKE 'latin1%';

 

MySQL Collation

MySQL Collations for latin1 Character Set

 

As mentioned above, each character set has at a default collation e.g., latin1_swedish_ci is the default collation for the latin1 character set.

Setting character sets and collations

MySQL allows you to specify character sets and collations at four levels: server, database, table, and column.

Setting character sets and collations at Server Level

Notice MySQL uses latin1 as the default character set, therefore, its default collation is latin1_swedish_ci. You can change these settings at server startup.

If you specify only a character set at server startup, MySQL will use the default collation of the character set. If you specify both a character set and a collation explicitly, MySQL will use the character set and collation for all databases created in the database server.

The following statement sets the utf8 character set and utf8_unicode_cs collation for the server via command line:

1

>mysqld --character-set-server=utf8 --collation-server=utf8_unicode_ci

 

Setting character sets and collations at the database level

When you create a database, if you do not specify its character set and collation, MySQL will use the default character set and collation of the server for the database.

You can override the default settings at the database level by using CREATE DATABASE or ALTER DATABASE statement as follows:

1

2

3

CREATE DATABASE database_name

CHARACTER SET character_set_name;

COLLATE collation_name

 

1

2

3

ALTER DATABASE database_name

CHARACTER SET character_set_name

COLLATE collation_name;

MySQL uses the character set and collation at the database level for all tables created within the database.

Setting character sets and collations at the table level

A database may contain tables with character sets and collations that are different from the default database’s character set and collation.

You can specify the default character set and collation for a table when you create the table by using the CREATE TABLE statement or when you alter the table’s structure by using the ALTER TABLE  statement.

1

2

3

4

5

CREATE TABLE table_name(

   ...

)

CHARACTER SET character_set_name

COLLATE collation_name

 

1

2

3

4

5

ALTER TABLE table_name(

  ...

)

CHARACTER SET character_set_name

COLLATE collation_name

 

Setting character set and collation at column level

A column of type CHAR , VARCHAR or TEXT can have its own character set and collation that is different from the default character set and collation of the table.

You can specify a character set and a collation for the column in the column’s definition of either CREATE TABLE or ALTER TABLE  statement as follows:

1

2

3

column_name [CHAR | VARCHAR | TEXT] (length)

CHARACTER SET character_set_name

COLLATE collation_name

These are the rules for setting the character set and collation:

  • If you specify both a character set and a collation explicitly, the character set and collation are used.
  • If you specify a character set and omit the collation, the default collation of the character set is used.
  • If you specify a collation without a character set, the character set associated with the collation is used.
  • If you omit both character set and collation, the default character set and collation are used.

Let’s take a look at some examples of setting the character sets and collations.

Examples of setting character sets and collations

First, we create a new database with utf8 as the character set and utf8_unicode_ci as the default collation:

1

2

3

CREATE DATABASE mydbdemo

CHARACTER SET utf8

COLLATE utf8_unicode_ci;

Because we specify the character set and collation for the mydbdemo database explicitly, the mydbdemo does not take the default character set and collation at the server level.

Second, we create a new table named t1 in the mydbdemo database:

1

2

3

4

USE mydbdemo; 

CREATE TABLE t1(

c1 char(25)

);

We did not specify the character set and collation for the t1 table; MySQL will check the database level to determine the character set and collation for the t1  table. In this case, the t1  table has utf8 as the default character set and utf8_unicode_ci as the default collation.

Third, for the t1  table, we change its character set to latin1 and its collation to latin1_german1_ci:

1

2

3

ALTER TABLE t1

CHARACTER SET latin1

COLLATE latin1_german1_ci;

The c1 column in the t1 table has latin1 as the character set and latin1_german1_ci as the collation.

Fourth, let’s change the character set of the c1  column to latin1 :

1

2

3

ALTER TABLE t2

MODIFY c1 VARCHAR(25)

CHARACTER SET latin1;

Now, the c1  column has the latin1  character set, but what about its collation? Is it inheriting the latin1_german1_ci collation from the table’s collation? No, because the default collation of the latin1character set is latin1_swedish_ci , the c1 column has the latin1_swedish_ci collation.

In this tutorial, you have learned about MySQL collation and how to specify character sets and collations for MySQL server, databases, tables and columns.

Reference

以下是对提供的参考资料的总结,按照要求结构化多个要点分条输出: 4G/5G无线网络优化与网规案例分析: NSA站点下终端掉4G问题:部分用户反馈NSA终端频繁掉4G,主要因终端主动发起SCGfail导致。分析显示,在信号较好的环境下,终端可能因节能、过热保护等原因主动释放连接。解决方案建议终端侧进行分析处理,尝试关闭节电开关等。 RSSI算法识别天馈遮挡:通过计算RSSI平均值及差值识别天馈遮挡,差值大于3dB则认定有遮挡。不同设备分组规则不同,如64T和32T。此方法可有效帮助现场人员识别因环境变化引起的网络问题。 5G 160M组网小区CA不生效:某5G站点开启100M+60M CA功能后,测试发现UE无法正常使用CA功能。问题原因在于CA频点集标识配置错误,修正后测试正常。 5G网络优化与策略: CCE映射方式优化:针对诺基亚站点覆盖农村区域,通过优化CCE资源映射方式(交织、非交织),提升RRC连接建立成功率和无线接通率。非交织方式相比交织方式有显著提升。 5G AAU两扇区组网:与三扇区组网相比,AAU两扇区组网在RSRP、SINR、下载速率和上传速率上表现不同,需根据具体场景选择适合的组网方式。 5G语音解决方案:包括沿用4G语音解决方案、EPS Fallback方案和VoNR方案。不同方案适用于不同的5G组网策略,如NSA和SA,并影响语音连续性和网络覆盖。 4G网络优化与资源利用: 4G室分设备利旧:面对4G网络投资压减与资源需求矛盾,提出利旧多维度调优策略,包括资源整合、统筹调配既有资源,以满足新增需求和提质增效。 宏站RRU设备1托N射灯:针对5G深度覆盖需求,研究使用宏站AAU结合1托N射灯方案,快速便捷地开通5G站点,提升深度覆盖能力。 基站与流程管理: 爱立信LTE基站邻区添加流程:未提供具体内容,但通常涉及邻区规划、参数配置、测试验证等步骤,以确保基站间顺畅切换和覆盖连续性。 网络规划与策略: 新高铁跨海大桥覆盖方案试点:虽未提供详细内容,但可推测涉及高铁跨海大桥区域的4G/5G网络覆盖规划,需考虑信号穿透、移动性管理、网络容量等因素。 总结: 提供的参考资料涵盖了4G/5G无线网络优化、网规案例分析、网络优化策略、资源利用、基站管理等多个方面。 通过具体案例分析,展示了无线网络优化的常见问题及解决方案,如NSA终端掉4G、RSSI识别天馈遮挡、CA不生效等。 强调了5G网络优化与策略的重要性,包括CCE映射方式优化、5G语音解决方案、AAU扇区组网选择等。 提出了4G网络优化与资源利用的策略,如室分设备利旧、宏站RRU设备1托N射灯等。 基站与流程管理方面,提到了爱立信LTE基站邻区添加流程,但未给出具体细节。 新高铁跨海大桥覆盖方案试点展示了特殊场景下的网络规划需求。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值