共計 12294 個字符，預計需要花費 31 分鐘才能閱讀完成。
丸趣 TV 小編給大家分享一下 MySQL 8.0 的新特性有哪些，希望大家閱讀完這篇文章之后都有所收獲，下面讓我們一起去探討吧！
一、地理信息系統 GIS
8.0 版本提供對地形的支持，其中包括了對空間參照系的數據源信息的支持，SRS aware spatial 數據類型，空間索引，空間函數。總而言之，8.0 版本可以理解地球表面的經緯度信息，而且可以在任意受支持的 5000 個空間參照系中計算地球上任意兩點之間的距離。
MySQL 8.0 delivers geography support. This includes meta-data support for Spatial Reference System (SRS), as well as SRS aware spatial datatypes, spatial indexes, and spatial functions. In short, MySQL 8.0 understands latitude and longitude coordinates on the earth rsquo;s surface and can, for example, correctly calculate the distances between two points on the earths surface in any of the about 5000 supported spatial reference systems.
空間參照系 Spatial Reference System (SRS)
ST_SPATIAL_REFERENCE_SYSTEMS 存在于 information schema 視圖庫中，提供了可供使用的 SRS 坐標系統的名稱。
每個 SRS 坐標系統都有一個 SRID 編號。8.0 版本支持 EPSG Geodetic Parameter Dataseset 中的 5 千多個坐標系統（包括立體模和 2D 平面地球模型）
The ST_SPATIAL_REFERENCE_SYSTEMS information schema view provides information about available spatial reference systems for spatial data. This view is based on the SQL/MM (ISO/IEC 13249-3) standard.
Each spatial reference system is identified by an SRID number. MySQL 8.0 ships with about 5000 SRIDs from the EPSG Geodetic Parameter Dataset, covering georeferenced ellipsoids and 2d projections (i.e. all 2D spatial reference systems).
SRID 地理數據類型 SRID aware spatial datatypes
空間類的數據類型可以直接從 SRS 坐標系統的定義中獲取，例如：使用 SRID 4326 定義進行建表： CREATE TABLE t1 (g GEOMETRY SRID 4326); 。
SRID 是適用于地理類型的數據類型。只有同一 SRID 的的數據才會被插入到行中。與當前 SRID 數據類型的數據嘗試插入時，會報錯。未定義 SRID 編號的表將可以接受所有 SRID 編號的數據。
Spatial datatypes can be attributed with the spatial reference system definition, for example with SRID 4326 like this: CREATE TABLE t1 (g GEOMETRY SRID 4326);
The SRID is here a SQL type modifier for the GEOMETRY datatype. Values inserted into a column with an SRID property must be in that SRID. Attempts to insert values with other SRIDs results in an exception condition being raised. Unmodified types, i.e., types with no SRID specification, will continue to accept all SRIDs, as before.
8.0 版本增加了 INFORMATION_SCHEMA.ST_GEOMETRY_COLUMNS 視圖，可以顯示當前實例中所有地理信息的數據行及其對應的 SRS 名稱，編號，地理類型名稱。
MySQL 8.0 adds
the INFORMATION_SCHEMA.ST_GEOMETRY_COLUMNS view as specified in SQL/MM Part 3, Sect. 19.2. This view will list all GEOMETRY columns in the MySQL instance and for each column it will list the standard SRS_NAME , SRS_ID , and GEOMETRY_TYPE_NAME.
SRID 空間索引 SRID aware spatial indexes
在空間數據類型上可以創建空間索引，創建空間索引的列必須非空，例如： CREATE TABLE t1 (g GEOMETRY SRID 4326 NOT NULL, SPATIAL INDEX(g));
Spatial indexes can be created on spatial datatypes. Columns in spatial indexes must be declared NOT NULL. For example like this: CREATE TABLE t1 (g GEOMETRY SRID 4326 NOT NULL, SPATIAL INDEX(g));
創建空間索引的列必須具有 SRID 數據標識以用于優化器使用，如果將空間索引建在沒有 SRID 數據標識的列上，將輸出 waring 信息。
Columns with a spatial index should have an SRID type modifier to allow the optimizer to use the index. If a spatial index is created on a column that doesn rsquo;t have an SRID type modifier, a warning is issued.
SRID 空間函數
8.0 增加了諸如 ST_Distance() 和 ST_Length() 等用于判斷數據的參數是否在 SRS 中，并計算其空間上的距離。到目前為止，ST_Distance 和其他的空間關系型函數諸如 ST_Within,ST_Intersects,ST_Contains,ST_Crosses 都支持地理計算。其運算邏輯與行為參見 SQL/MM Part 3 Spatial
MySQL 8.0 extends spatial functions such as ST_Distance() and ST_Length() to detect that its parameters are in a geographic (ellipsoidal) SRS and to compute the distance on the ellipsoid. So far, ST_Distance and spatial relations such as ST_Within, ST_Intersects, ST_Contains, ST_Crosses, etc. support geographic computations. The behavior of each ST function is as defined in SQL/MM Part 3 Spatial.
二、字符集 Character Sets
8.0 版本默認使用 UTF8MB4 作為默認字符集。相比較 5.7 版本，SQL 性能（諸如排序 UTF8MB4 字符串）得到了很大的提升。UTF8MB4 類型在網頁編碼上正占據著舉足輕重的地位，將其設為默認數據類型后，將會給絕大多數的 MySQL 用戶帶來便利。
MySQL 8.0 makes UTF8MB4 the default character set. SQL performance ndash; such as sorting UTF8MB4 strings ndash; has been improved by a factor of 20 in 8.0 as compared to 5.7. UTF8MB4 is the dominating character encoding for the web, and this move will make life easier for the vast majority of MySQL users.
默認的字符集從 latin1 變為 utf8mb4 , 默認排序校對規則從 latin1_swedish_ci 變為 utf8mb4_800_ci_ai。
The default character set has changed from latin1 to utf8mb4 and the default collation has changed from latin1_swedish_ci to utf8mb4_800_ci_ai.
utf8mb4 同樣也成為 libmysql，服務端命令行工具,server 層的默認編碼
The changes in defaults applies to libmysql and server command tools as well as the server itself.
utf8mb4 同樣也成為 MySQL 測試框架的默認編碼
The changes are also reflected in MTR tests, running with new default charset.
排序校對規則的權重與大小寫基于 Unicode 委員會 16 年公布的 Unicode 9.0.0 版本。
The collation weight and case mapping are based on Unicode 9.0.0 , announced by the Unicode committee on Jun 21, 2016.
在以往的 MySQL 版本中，latin1 編碼中的 21 種語言的特殊大小寫和排序校對規則被引入了 utf8mb4 排序校對規則。例如：捷克語的排序校對規則變成了 utf8mb4_cs_800_ai_ci。
The 21 language specific case insensitive collations available for latin1 (MySQL legacy) have been implemented forutf8mb4 collations, for example the Czech collation becomes utf8mb4_cs_800_ai_ci. See complete list in WL#9108 . See blog post by Xing Zhang here .
增加了對特殊語境和重音敏感的排序校對規則的支持。8.0 版本支持 DUCET (Default Unicode Collation Entry Table) 全部三級排序校對規則。
Added support for case and accent sensitive collations. MySQL 8.0 supports all 3 levels of collation weight defined by DUCET (Default Unicode Collation Entry Table). See blog post by Xing Zhang here.
utf8mb4 的 utf8mb4_ja_0900_as_cs 排序校驗規則對日語字符支持三級權重的排序。
Japanese utf8mb4_ja_0900_as_cs collation for utf8mb4 which sorts characters by using three levels rsquo; weight. This gives the correct sorting order for Japanese. See blog post by Xing Zhang here.
對日語有額外的假名支持特性， utf8mb4_ja_0900_as_cs_ks 中的 ks 表示假名區分。
Japanese with additional kana sensitive feature, utf8mb4_ja_0900_as_cs_ks, where lsquo;ks rsquo; stands for lsquo;kana sensitive rsquo;. See blog post by Xing Zhang here.
把 Unicode 9.0.0 之前所有排序校驗規則中的不填補變成填補字符，此舉有利于提升字符串的一致性和性能。例如把字符串末尾的空格按照其他字符對待。之前的排序校驗規則在處理這種情況時保留字符串原樣。
Changed all new collations, from Unicode 9.0.0 forward, to be NO PAD instead of PAD STRING, ie., treat spaces at the end of a string like any other character. This is done to improve consistency and performance. Older collations are left in place.
See also blog posts by Bernt Marius Johnsen here, here and here.
三、數據類型 Datatypes 二進制數據類型的 Bit-wise 操作
8.0 版本擴展了 bit-wise 操作（如 bit-wise AND 等）的使用范圍，使得其在所有 BINARY 數據類型上都適用。在此之前只支持整型數據，若強行在二進制數據類型上使用 Bit-wise 操作，將會隱式轉換為 64 位的 BITINT 類型，并可能丟失若干位的數據。
從 8.0 版本之后，bit-wise 操作可以在 BINARY 和 BLOB 類型上使用，且不用擔心精確度下降的問題。
MySQL 8.0 extends the bit-wise operations (lsquo;bit-wise AND rsquo;, etc) to also work with [VAR]BINARY/[TINY|MEDIUM|LONG]BLOB. Prior to 8.0 bit-wise operations were only supported for integers. If you used bit-wise operations on binaries the arguments were implicitly cast to BIGINT (64 bit) before the operation, thus possibly losing bits.
From 8.0 and onward bit-wise operations work for all BINARY and BLOB data types, casting arguments such that bits are not lost.
IPV6 操作
8.0 版本通過支持 BINARY 上的 Bit-wise 操作提升了 IPv6 數據的可操作性。5.6 版本中引入了支持 IPv6 地址和 16 位二進制數據的互相轉換的 INET6_ATON() 和 INET6_NTOA() 函數。
但是直到 8.0 之前，由于上一段中的問題我們都無法講 IPv6 轉換函數和 bit-wise 操作結合起來。由于 INET6_ATON() 可以正確的返回 128bit 的 VARBINARY(16)，如果我們想要將一個 IPv6 地址與網關地址進行比對，現在就可以使用 INET6_ATON(address) INET6_ATON(network) 操作。
MySQL 8.0 improves the usability of IPv6 manipulation supporting bit-wise operations on BINARY data types. In MySQL 5.6 we introduced the INET6_ATON() and INET6_NTOA() functions which convert IPv6 addresses between text form like fe80::226:b9ff:fe77:eb17 and VARBINARY(16).
However, until now we could not combine these IPv6 functions with bit-wise operations since such operations would ndash; wrongly ndash; convert output to BIGINT. For example, if we have an IPv6 address and want to test it against a network mask, we can now use INET6_ATON(address) INET6_ATON(network) because INET6_ATON() correctly returns the VARBINARY(16)datatype (128 bits). See blog post by Catalin Besleaga here.
UUID 操作
8.0 版本通過增加了三個新的函數（UUID_TO_BIN(), BIN_TO_UUID(), 和 IS_UUID()）提升了 UUID 的可用性。UUID_TO_BIN() 可以將 UUID 格式的文本轉換成 VARBINARY(16), BIN_TO_UUID() 則與之相反， IS_UUID() 用來校驗 UUID 的有效性。將 UUID 以 VARBINARY(16) 的方式存儲后，就可以使用實用的索引了。
UUID_TO_BIN() 函數可以原本轉換后的二進制數值中的時間相關位（UUID 生成時有時間關聯）移到數據的開頭，這樣對索引來說更加友好而且可以減少在 B 樹中的隨機插入，從而減少了插入耗時。
MySQL 8.0 improves the usability of UUID manipulations by implementing three new SQL functions: UUID_TO_BIN(), BIN_TO_UUID(), and IS_UUID(). The first one converts from UUID formatted text to VARBINARY(16), the second one from VARBINARY(16) to UUID formatted text, and the last one checks the validity of an UUID formatted text. The UUID stored as a VARBINARY(16) can be indexed using functional indexes.
The functions UUID_TO_BIN() and UUID_TO_BIN() can also shuffle the time-related bits and move them at the beginning making it index friendly and avoiding the random inserts in the B-tree, this way reducing the insert time. The lack of such functionality has been mentioned as one of the drawbacks of using UUID rsquo;s. See blog post by Catalin Besleaga here.
四、消耗敏感的模型 查詢優化器將會照顧到數據緩沖的狀況
8.0 版本自動地根據數據是否存在于內存中而選擇查詢計劃，在以往的版本中，消耗敏感的模型始終假設數據在磁盤上。
正因為現在查詢內存數據和查詢硬盤數據的消耗常數不同，因此優化器會根據數據的位置選擇更加優化的讀取數據方式。
MySQL 8.0 chooses query plans based on knowledge about whether data resides in-memory or on-disk. This happens automatically, as seen from the end user there is no configuration involved. Historically, the MySQL cost model has assumed data to reside on spinning disks.
The cost constants associated with looking up data in-memory and on-disk are now different, thus, the optimizer will choose more optimal access methods for the two cases, based on knowledge of the location of data. See blog post by Oslash;ystein Gr oslash;vlen here.
查詢優化器的直方圖
8.0 版本加入了直方圖統計數據。用戶可以根據直方圖針對表中的某列（一般為非索引列）生成數據分布統計信息，這樣優化器就可以利用這些信息去尋覓更加優化的查詢計劃。
直方圖最常見的使用場景就是計算字段的選擇性。
MySQL 8.0 implements histogram statistics. With Histograms, the user can create statistics on the data distribution for a column in a table, typically done for non-indexed columns, which then will be used by the query optimizer in finding the optimal query plan.
The primary use case for histogram statistics is for calculating the selectivity (filter effect) of predicates of the form“COLUMN operator CONSTANT”.
用以創建直方圖的 ANALYZE TABLE 語法現已被擴展了兩個新子句： UPDATE HISTOGRAM ON column [, column] [WITH n BUCKETS] 和 DROP HISTOGRAM ON column [, column]。
直方圖的總計總數（桶）是可以選的，默認 100。直方圖的統計信息被存儲在詞典表 column_statistics 中，并可以使用
information_schema.COLUMN_STATISTICS 進行查看。由于 JSON 數據格式的靈活性，直方圖現在以 JSON 對象存儲。
根據表的大小，ANALYZE TABLE 命令會自動的判斷是否要表進行采樣，甚至會根據表中數據的分布情況和統計總量來決定創建等頻或者等高的直方圖。
The user creates a histogram by means of the ANALYZE TABLE syntax which has been extended to accept two new clauses: UPDATE HISTOGRAM ON column [, column] [WITH n BUCKETS] and DROP HISTOGRAM ON column [, column].
The number of buckets is optional, the default is 100. The histogram statistics are stored in the dictionary table“column_statistics”and accessible through the view information_schema.COLUMN_STATISTICS. The histogram is stored as a JSON object due to the flexibility of the JSON datatype.
ANALYZE TABLE will automatically decide whether to sample the base table or not, based on table size. It will also decide whether to build a singleton or a equi-height histogram based on the data distribution and the number of buckets specified. See blog post by Erik Fr oslash;seth here.
五、正則表達式
與 UTF8MB4 的正則支持一同，8.0 版本也增加了諸如 REGEXP_INSTR(), REGEXP_LIKE(), REGEXP_REPLACE(), 和 REGEXP_SUBSTR() 等新函數。
另外，系統中還增加了用以控制正則表達式致性的 regexp_stack_limit (默認 8000000 比特) 和 regexp_time_limit (默認 32 步) 參數。REGEXP_REPLACE() 也是社區中受呼聲比較高的特性。
MySQL 8.0 supports regular expressions for UTF8MB4 as well as new functions like REGEXP_INSTR(), REGEXP_LIKE(), REGEXP_REPLACE(), and REGEXP_SUBSTR().
The system variables regexp_stack_limit (default 8000000 bytes) and regexp_time_limit (default 32 steps) have been added to control the execution. The REGEXP_REPLACE() function is one of the most requested features by the MySQL community, for example see feature request reported as BUG #27389 by Hans Ginzel. See also blog posts by Martin Hansson here and Bernt Marius Johnsen here.
六、運維自動化特性
開發向的運維關心數據庫實例的可操作型，通常即可靠性，可用性，性能，安全，可觀測性，可管理性。關于 InnoDB Cluster 和 MGR 的可靠性我們將會另起新篇單獨介紹，接下來的段落將會介紹關于 8.0 版本針對表在其他可操作性上的改變。
Dev Ops care about operational aspects of the database, typically about reliability, availability, performance, security, observability, and manageability. High Availability comes with MySQL InnoDB Cluster and MySQL Group Replication which will be covered by a separate blog post. Here follows what 8.0 brings to the table in the other categories.
七、可靠性
8.0 版本在整體上 增加了可靠性，原因如下：
MySQL 8.0 increases the overall reliability of MySQL because :
1、8.0 版本將元信息存儲與久經考驗的事務性存儲引擎 InnoDB 中。諸如用戶權限表，數據字典表，現在都使用 InnoDB 進行存儲。
MySQL 8.0 stores its meta-data into InnoDB, a proven transactional storage engine. System tables such as Users and Privileges as well as Data Dictionary tables now reside in InnoDB.
2、8.0 版本消除了會導致非一致性的一處隱患。在 5.7 及以前的版本中，存在著服務層和引擎層兩份數據字典，因而可能導致在故障情況下的數據字典間的同步失敗。在 8.0 版本中，只有一份數據字典。
MySQL 8.0 eliminates one source of potential inconsistency. In 5.7 and earlier versions there are essentially two data dictionaries, one for the Server layer and one for the InnoDB layer, and these can get out of sync in some crashing scenarios. In 8.0 there is only one data dictionary.
3、8.0 版本實現了原子化，無懼宕機的 DDL。根據這個特性，DDL 語句要么被全部執行，要么全部未執行。對于復制環境來說這是至關重要的，否則會導致主從之間因為表結構不一致，數據漂移的情況。
MySQL 8.0 ensures atomic, crash safe DDL. With this the user is guaranteed that any DDL statement will either be executed fully or not at all. This is particularly important in a replicated environment, otherwise there can be scenarios where masters and slaves (nodes) get out of sync, causing data-drift.
基于新的事務型數據字典，可靠性得到了提高。
This work is done in the context of the new, transactional data dictionary. See blog posts by Staale Deraas here and here.
看完了這篇文章，相信你對“MySQL 8.0 的新特性有哪些”有了一定的了解，如果想了解更多相關知識，歡迎關注丸趣 TV 行業資訊頻道，感謝各位的閱讀！
