Mysql:Changes in MySQL 5.7.13 (2016-06-02, General Availability):maximum length of MySQL user names was increased from 16 to 32 characters

Changes in MySQL 5.7.13 (2016-06-02, General Availability)

Account Management Notes

  • In MySQL 5.7.8, the maximum length of MySQL user names was increased from 16 to 32 characters, but some applicable contexts for this increase were overlooked. Additional changes in maximum user name length now have been applied:

    • The size of these mysql system table columns is increased:

      • The definer column of the event and proc tables
      • The grantor column of the procs_priv and tables_priv tables

      In each case, the column previously was defined as CHAR(77), where 77 was chosen to permit a user_name@host_name string containing a user name up to 16 characters, a @ character, and a host name up to 60 characters. Each column now is defined as CHAR(93), reflecting an increase in permitted user name length from 16 to 32 characters.

    • A similar change from CHAR(77) to CHAR(93)applies to the DEFINER column of these INFORMATION_SCHEMA tables: EVENTS, ROUTINES, TRIGGERS, VIEWS. Along with the changes to INFORMATION_SCHEMA tables, output from any corresponding SHOW statements now displays DEFINER values up to 93 characters. Examples of affected statements: SHOW EVENTS, SHOW TRIGGERS, SHOW PROCEDURE STATUS.

    If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate the changes to the mysql system database. A server from MySQL 5.7.13 or higher for which mysql_upgrade has not been run continues to permit a maximum of 77 characters in the system tables mentioned previously, and an ER_USER_COLUMN_OLD_LENGTH error will occur in those system table contexts where a user_name@host_name value from 78 to 93 characters long is given.

  • It is possible to use ALTER TABLE to change the default
    value of a column col_name, which may
    change the value of a generated column expression that refers to the column
    using DEFAULT(col_name). For this reason, ALTER TABLE operations that change
    the definition of a column now cause a table rebuild if any generated column
    expression uses DEFAULT(). (Bug #80299, Bug
    #22680839)

It is possible to use ALTER TABLE to change the default
value of a column col_name, which may
change the value of a generated column expression that refers to the column
using DEFAULT(col_name). For this reason, ALTER TABLE operations that change
the definition of a column now cause a table rebuild if any generated column
expression uses DEFAULT().

原文地址:https://www.cnblogs.com/jinzhenshui/p/12584082.html

时间: 2024-10-08 05:00:00

Mysql:Changes in MySQL 5.7.13 (2016-06-02, General Availability):maximum length of MySQL user names was increased from 16 to 32 characters的相关文章

Mysql:Changes in MySQL 5.7.9 (2015-10-21, General Availability):很重要的版本!

Changes in MySQL 5.7.9 (2015-10-21, General Availability) Server Administration A new SHUTDOWN SQL statement is available. This provides an SQL-level interface to the same functionality previously available using the mysqladmin shutdown command or th

Mysql:Changes in MySQL 5.6.22 (2014-12-01, General Availability):【sql-log-bin】

Changes in MySQL 5.6.22 (2014-12-01, General Availability) Deprecation and Removal Notes Replication: The global scope for the sql_log_bin system variable has been deprecated, and this variable can now be set with session scope only. The statement SE

Mysql:Changes in MySQL 5.6.30 (2016-04-11, General Availability):--ssl-mode:

Changes in MySQL 5.6.30 (2016-04-11, General Availability) Security Notes The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1s. For a description of issues fixed in this version, see http://www.openssl.org/new

Mysql:Changes in MySQL 5.6.34 (2016-10-12, General Availability):secure-file-priv

Changes in MySQL 5.6.34 (2016-10-12, General Availability) Security Notes Incompatible Change: The secure_file_priv system variable is used to limit the effect of data import and export operations. The following changes have been made to how the serv

Maximum length of a table name in MySQL

http://dev.mysql.com/doc/refman/5.7/en/identifiers.html The following table describes the maximum length for each type of identifier. Identifier Maximum Length (characters) Database 64 (NDB storage engine: 63) Table 64 (NDB storage engine: 63) Column

PHP连接数据库错误:Can't connect to MySQL server on '127.0.0.1' (13)2003

学习PHP中的.今天学习php连接数据库,代码如下:    <?php       $link = mysql_connect("127.0.0.1","root","123456");         if($link) {             echo '数据源连接成功';         }         else {             echo "数据库连接失败,请检查帐户密码".  mysql_er

MySql之centos7.2安装mysql5.7.13

一.MySQL 5.7主要特性: 原生支持Systemd更好的性能:对于多核CPU.固态硬盘.锁有着更好的优化更好的InnoDB存储引擎更为健壮的复制功能:复制带来了数据完全不丢失的方案,传统金融客户也可以选择使用MySQL数据库. 新增sys库:以后这会是DBA访问最频繁的库更好的优化器:优化器代码重构的意义将在这个版本及以后的版本中带来巨大的改进,Oracle官方正在解决MySQL之前最大的难题原生JSON类型的支持(JavaScript Object Notation) 注:JSON(Ja

MySQL 数据库连接失败 SQLSTATE[HY000] [2003] Can&#39;t connect to MySQL server on &#39;127.0.0.1&#39; (13)

CentOS6.5x64 安装禅道6.2,生成配置文件,数据库连接失败 数据库连接失败 SQLSTATE[HY000] [2003] Can't connect to MySQL server on '127.0.0.1' (13) root,密码肯定没有错(命令行可以登录),用的127.0.0.1 PHP安装正常,MySQL配置正确,PHP的PDO.MySQL扩展正确,使用 <?php $link=mysql_connect('localhost','root','password'); if

MySQL启动故障处理一例(errno 13)

之前在系统上装了个MySQL用于测试,今天发现启动mysqld_safe进程的时候报错,如下所示: [[email protected] local]# mysqld_safe & [1] 2631 [[email protected] local]# Starting mysqld daemon with databases from /data/mysql/mysql_3306/data STOPPING server from pid file /data/mysql/mysql_3306