New in MySQL 8.0 - the Vanishing Parameters, Features...

This article summarizes the parameters and features removed in the first version of MySQL 8.0. Some parameters and features are currently set to deprecated in MySQL 8.0. Some others have been set to deprecated in MySQL 5.7 or earlier versions, but are removed from the code in MySQL 8.0.

MySQL 8.0.0

WL#7704:InnoDB: Remove deprecated file format parameters in 8.0

The purpose of supporting file-format configuration is to stay compatible with earlier versions. In versions earlier than MySQL 8.0, two primary file formats are supported:

1. Antelope: The corresponding row format is: COMPACT and REDUNDANT.

2. Barracuda: the new file format. The corresponding row format is: COMPRESSED and DYNAMIC.

Since earlier versions have passed the deadline for long-time maintenance, the old file formats are not maintained in MySQL 8.0 any more.

So removing the old code is helpful to clarify the code structure.

Several parameters related to file_format are removed:

innodb_file_format
innodb_file_format_check
innodb_file_format_max
innodb_large_prefix

Columns related to file-format in INFORMATION_SCHEMA are removed:

   innodb_sys_tables

After the code is committed, a large amount of code is erased and the structure looks much clearer.

WL#8157: Remove deprecated GIS functions

Old functions related to GIS are removed. New functions are replaced with ST_xxx. A total of 67 functions are removed, including their test cases.

WL#8843: Deprecate and remove the parameter innodb_support_xa

Parameter innodb_support_xa is removed. The reason is that this parameter has been invalid. On the one hand, when XA is set to OFF, PREPARE transactions can only be rolled back and cannot be committed; on the other hand, the data consistency of Binlog/Engine failure recovery should be ensured.

After this parameter is removed, the XA is enabled by default.

WL#8894: InnoDB: Remove deprecated parameter innodb_locks_unsafe_for_binlog

The same as above, the parameter innodb_locks_unsafe_for_binlog has been marked as deprecated in MySQL 5.6 and is removed from the code in MySQL 8.0. (The instruction document of the parameter. But again, I guess no one will set it in normal cases.)

WL#9071: Remove mysql_install_db and server --bootstrap option

The mysql_install_db is removed and the bootstrap parameter of mysqld is also deleted. In future, to install instances, you need to usemysqld --initialize

WL#9014: Deprecate and remove mysql_shutdown()

The C API mysql_shutdown is deleted and the Command type COM_SHUTDOWN is deleted.COM_SHUTDOWN

WL#9091: Remove --ssl, --ssl-verify-server-cert client-side options

The --ssl, --ssl-verify-server-cert client-side options are removed. In future, you can use --ssl-mode options implemented by WL#8785.

时间: 2024-11-01 09:51:54

New in MySQL 8.0 - the Vanishing Parameters, Features...的相关文章

MYSQL 6.0的新特点预览

* 对子查询和Join进行了优化,包括对MyISAD和InnoB存储引擎分散范围内的批量索引访问. * 增加了 BACKUP DATABASE 和 RESTORE 语句来进行备份和还原操作. 见第6.3节, "使用MySQL备份" . * 支持更多的Unicode字符集: utf16 , utf32 ,和4字节utf8 . 这些字符集支持这些附加的Unicode字符集,也就是那些在基础多语言基础之外的字符) . * 新Falcon事务存储引擎(见 13.8, "Falcon存

MySQL 5.0新特性教程 存储过程:第二讲

Why MySQL Statements are Legal in a Procedure Body 什么MySQL语句在存储过程体中是合法的? 什么样的SQL语句在Mysql存储过程中才是合法的呢?你可以创建一个包含INSERT, UPDATE,DELETE, SELECT, DROP, CREATE, REPLACE等的语句.你唯一需要记住的是如果代码中包含MySQL扩充功能,那么代码将不能移植.在标准SQL语句中:任何数据库定义语言都是合法的,如: CREATE PROCEDURE p (

MySQL 5.0新特性教程 存储过程:第一讲

mysql|存储过程|教程 作者:mysql AB;翻译:陈朋奕 Introduction 简介 MySQL 5.0 新特性教程是为需要了解5.0版本新特性的MySQL老用户而写的.简单的来说是介绍了"存储过程.触发器.视图.信息架构视图",在此感谢译者陈朋奕的努力. 希望这本书能像内行专家那样与您进行对话,用简单的问题.例子让你学到需要的知识.为了达到这样的目的,我会从每一个细节开始慢慢的为大家建立概念,最后会给大家展示较大的实用例,在学习之前也许大家会认为这个用例很难,但是只要跟着

MySQL 5.0新特性教程 存储过程:第一讲

Introduction 简介 MySQL 5.0 新特性教程是为需要了解5.0版本新特性的MySQL老用户而写的.简单的来说是介绍了"存储过程.触发器.视图.信息架构视图",在此感谢译者陈朋奕的努力. 希望这本书能像内行专家那样与您进行对话,用简单的问题.例子让你学到需要的知识.为了达到这样的目的,我会从每一个细节开始慢慢的为大家建立概念,最后会给大家展示较大的实用例,在学习之前也许大家会认为这个用例很难,但是只要跟着课程去学,相信很快就能掌握. Conventions and St

MySQL · 8.0新特性 · New data dictionary尝鲜篇

众所周知,由于MySQL采用统一Server层+不同的底层引擎插件的架构模式,在Server层为每个表创建了frm文件,以保存与表定义相关的元数据信息.然而某些引擎(例如InnoDB)本身也会存储元数据,这样不仅产生了元数据冗余,而且由于Server层和引擎层分别各自管理,在执行DDL之类的操作时,很难做到crash-safe,更别说让DDL具备事务性了. 为了解决这些问题(尤其是DDL无法做到atomic),从MySQL8.0开始取消了FRM文件及其他server层的元数据文件(frm, pa

MySQL 5.0 新特性--存储过程(1)

Introduction 简介 MySQL 5.0 新特性教程是为需要了解5.0版本新特性的MySQL老用户而写的.简单的来说是介绍了"存储过程.触发器.视图.信息架构视图",在此感谢译者陈朋奕的努力. 希望这本书能像内行专家那样与您进行对话,用简单的问题.例子让你学到需要的知识.为了达到这样的目的,我会从每一个细节开始慢慢的为大家建立概念,最后会给大家展示较大的实用例,在学习之前也许大家会认为这个用例很难,但是只要跟着课程去学,相信很快就能掌握. Conventions and St

怎样解决MySQL 5.0.16的乱码问题

问:怎样解决MySQL 5.0.16的乱码问题? 答:MySQL 5.0.16的乱码问题可以用下面的方法解决: 1.设置phpMyAdmin Language:Chinese simplified (zh-utf-8) MySQL 字符集:UTF-8 Unicode (utf8) MySQL 连接校对 gbk_chinese_ci 2.创建数据库时 整理设置成 gbk_chinese_ci 3.用SQL建立表中 ENGINE=MyISAM DEFAULT CHARSET=gbk; ENGINE=

修改Linux下mysql 5.0.xx默认连接数

这段时间服务器崩溃2次,一直没有找到原因,今天看到论坛发出的错误信息邮件,想起可能是mysql的默认连接数引起的问题,一查果然,老天,默认连接数才100, 怎么够呀,在网上找了半天资料,有说修改my.cnf的,有说修改safe_mysqld,试了,前者无用,后者文件找不到:)原来是以前的版本跟现在的版本有所不同. 言归正传.我以centos 4.4 下面的mysql 5.0.33 手工编译版本为例说明: vi /usr/local/mysql/bin/mysqld_safe 找到safe_mys

MySQL 4.0 升级到5.0

由于需要,从4.0直接升级到5.0,查看了一下changelog,发现主要有以下变化: 一.从 4.0 到 4.1 的主要变化 如果在4.1.0到4.1.3版本的MySQL中创建了包含 TIMESTAMP 字段的 InnoDB 表.则在升级到4.1.4及更高时需要重建表,因为存储格式发生变化了 字符串根据标准SQL来比较:比较之前不删除末尾的空格,以前用末尾空格扩展了比较短的字符串.现在的结果是 'a' > 'a ',以前则不这样.可以用 mysqlcheck 来检查一下数据表 TIMESTAM