想修改MySQL 8.0用户的密码，按照如下操作
use mysql;
update user set password=password('123') where user='john';
flush privileges;
结果遇到报错：
> 1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '("123") where user='john'' at line 1
查了官方参考手册后发现password()函数在MySQL 8.0中已被弃用（见下面红字部分），改用如下语法：
(不需要use mysql;)
alter user 'john'@'localhost' identified with mysql_native_password by '123';
flush privileges;
注意，'john'不一定是@'localhost'，也可能是@'%'，这取决于你的设置。如果弄错，则会遇到报错：
1396 - Operation ALTER USER failed for 'john'@'localhost'.
with mysql_native_password可以不加，即上面的语句可以写成alter user 'john'@'localhost' identified by '123';
with后面可以跟caching_sha2_password / mysql_native_password / sha256_password
Features Deprecated in MySQL 8.0
The following features are deprecated in MySQL 8.0 and may be or will be removed in a future series. Where alternatives are shown, applications should be updated to use them.
For applications that use features deprecated in MySQL 8.0 that have been removed in a higher MySQL series, statements may fail when replicated from a MySQL 8.0 master to a higher-series slave, or may have different effects on master and slave. To avoid such problems, applications that use features deprecated in 8.0 should be revised to avoid them and use alternatives when possible.
• The validate_password plugin has been reimplemented to use the server component infrastructure. The plugin form of validate_password is still available but is deprecated and will be removed in a future version of MySQL. MySQL installations that use the plugin should make the transition to using the component instead. See Section 6.5.3.3, “Transitioning to the Password Validation Component”.
• The ALTER TABLESPACE and DROP TABLESPACE ENGINE clause is deprecated.
• The PAD_CHAR_TO_FULL_LENGTH SQL mode is deprecated. It will be removed in a future version of MySQL.
• The JSON_MERGE() function is deprecated. Use JSON_MERGE_PRESERVE() instead.
Features Removed in MySQL 8.0
The following items are obsolete and have been removed in MySQL 8.0. Where alternatives are shown, applications should be updated to use them.
For MySQL 5.7 applications that use features removed in MySQL 8.0, statements may fail when replicated from a MySQL 5.7 master to a MySQL 8.0 slave, or may have different effects on master and slave. To avoid such problems, applications that use features removed in MySQL 8.0 should be revised to avoid them and use alternatives when possible.
• The information_schema_stats configuration option, introduced in MySQL 8.0.0, was removed and replaced by information_schema_stats_expiry in MySQL 8.0.3.
information_schema_stats_expiry defines an expiration setting for cached INFORMATION_SCHEMA table statistics. For more information, see Section 8.2.3, “Optimizing INFORMATION_SCHEMA Queries”.
• Code related to obsoleted InnoDB system tables was removed in MySQL 8.0.3. INFORMATION_SCHEMA views based on InnoDB system tables were replaced by internal system views on data dictionary tables. Affected InnoDB INFORMATION_SCHEMA views were renamed:
Table 1.1 Renamed InnoDB Information Schema Views
| Old Name | New Name |
|---|---|
| INNODB_SYS_COLUMNS | INNODB_COLUMNS |
| INNODB_SYS_DATAFILES | INNODB_DATAFILES |
| INNODB_SYS_FIELDS | INNODB_FIELDS |
| INNODB_SYS_FOREIGN | INNODB_FOREIGN |
| INNODB_SYS_FOREIGN_COLS | INNODB_FOREIGN_COLS |
| INNODB_SYS_INDEXES | INNODB_INDEXES |
| INNODB_SYS_TABLES | INNODB_TABLES |
| INNODB_SYS_TABLESPACES | INNODB_TABLESPACES |
| INNODB_SYS_TABLESTATS | INNODB_TABLESTATS |
| INNODB_SYS_VIRTUAL | INNODB_VIRTUAL |
After upgrading to MySQL 8.0.3 or later, update any scripts that reference previous InnoDB INFORMATION_SCHEMA view names.
• The following features related to account management have been removed:
• Using GRANT to create users. Instead, use CREATE USER. Following this practice makes the
NO_AUTO_CREATE_USER SQL mode immaterial for GRANT statements, so it too is removed.
• Using GRANT to modify account properties other than privilege assignments. This includes authentication, SSL, and resource-limit properties. Instead, establish such properties at account- creation time with CREATE USER or modify them afterward with ALTER USER.
• IDENTIFIED BY PASSWORD 'hash_string' syntax for CREATE USER and GRANT. Instead, use IDENTIFIED WITH auth_plugin AS 'hash_string' for CREATE USER and ALTER USER, where the 'hash_string' value is in a format compatible with the named plugin.
Additionally, because IDENTIFIED BY PASSWORD syntax has been removed, the log_builtin_as_identified_by_password system variable is superfluous and has been removed.
• The PASSWORD() function. Additionally, PASSWORD() removal means that SET PASSWORD ...
= PASSWORD('auth_string') syntax is no longer available.
• The old_passwords system variable.
• The query cache has been removed. Removal includes these items:
• The FLUSH QUERY CACHE and RESET QUERY CACHE statements.
• These system variables: query_cache_limit, query_cache_min_res_unit, query_cache_size, query_cache_type, query_cache_wlock_invalidate.
• These status variables: Qcache_free_blocks, Qcache_free_memory, Qcache_hits, Qcache_inserts, Qcache_lowmem_prunes, Qcache_not_cached, Qcache_queries_in_cache, Qcache_total_blocks.
• These thread states: checking privileges on cached query, checking query cache for query, invalidating query cache entries, sending cached result to client, storing result in query cache, Waiting for query cache lock.
These deprecated query cache items remain deprecated, but have no effect, and will be removed in a future MySQL release:
• The SQL_CACHE and SQL_NO_CACHE SELECT modifiers.
• The ndb_cache_check_time system variable.
The have_query_cache system variable remains deprecated, always has a value of NO, and will be removed in a future MySQL release.
• The data dictionary provides information about database objects, so the server no longer checks directory names in the data directory to find databases. Consequently, the --ignore-db-dir option and ignore_db_dirs system variables are extraneous and have been removed.
• The tx_isolation and tx_read_only system variables have been removed. Use
transaction_isolation and transaction_read_only instead.
• The sync_frm system variable has been removed because .frm files have become obsolete.
• The secure_auth system variable and --secure-auth client option have been removed. The
MYSQL_SECURE_AUTH option for the mysql_options() C API function was removed.
• The multi_range_count system variable has been removed.
• The log_warnings system variable and --log-warnings server option have been removed. Use the log_error_verbosity system variable instead.
• The global scope for the sql_log_bin system variable has been removed. sql_log_bin has session scope only, and applications that rely on accessing @@global.sql_log_bin should be adjusted.
• The metadata_locks_cache_size and metadata_locks_hash_instances system variables have been removed.
• The unused date_format, datetime_format, time_format, and max_tmp_tables system variables have been removed.
• These deprecated compatibility SQL modes have been removed: DB2, MAXDB, MSSQL, MYSQL323, MYSQL40, ORACLE, POSTGRESQL, NO_FIELD_OPTIONS, NO_KEY_OPTIONS, NO_TABLE_OPTIONS. They can no longer be assigned to the sql_mode system variable or used as permitted values for the mysqldump --compatible option.
Removal of MAXDB means that the TIMESTAMP data type for CREATE TABLE or ALTER TABLE is treated as TIMESTAMP, and is no longer treated as DATETIME.
• The deprecated ASC or DESC qualifiers for GROUP BY clauses have been removed. Queries that previously relied on GROUP BY sorting may produce results that differ from previous MySQL versions. To produce a given sort order, provide an ORDER BY clause.
• The EXTENDED and PARTITIONS keywords for the EXPLAIN statement have been removed. These keywords are unnecessary because their effect is always enabled.
• These encryption-related items have been removed:
• The ENCODE() and DECODE() functions.
• The ENCRYPT() function.
• The DES_ENCRYPT(), and DES_DECRYPT() functions, the --des-key-file option, the have_crypt system variable, the DES_KEY_FILE option for the FLUSH statement, and the HAVE_CRYPT CMake option.
In place of the removed encryption functions: For ENCRYPT(), consider using SHA2() instead for one-way hashing. For the others, consider using AES_ENCRYPT() and AES_DECRYPT() instead.
• In MySQL 5.7, several spatial functions available under multiple names were deprecated to move in the direction of making the spatial function namespace more consistent, the goal being that each spatial function name begin with ST_ if it performs an exact operation, or with MBR if it performs an operation based on minimum bounding rectangles. In MySQL 8.0, the deprecated functions are removed to leave only the corresponding ST_ and MBR functions:
• These functions are removed in favor of the MBR names: Contains(), Disjoint(), Equals(), Intersects(), Overlaps(), Within().
• These functions are removed in favor of the ST_ names: Area(), AsBinary(), AsText(), AsWKB(), AsWKT(), Buffer(), Centroid(), ConvexHull(), Crosses(), Dimension(), Distance(), EndPoint(), Envelope(), ExteriorRing(), GeomCollFromText(), GeomCollFromWKB(), GeomFromText(), GeomFromWKB(), GeometryCollectionFromText(), GeometryCollectionFromWKB(), GeometryFromText(), GeometryFromWKB(), GeometryN(), GeometryType(), InteriorRingN(), IsClosed(), IsEmpty(), IsSimple(), LineFromText(),
LineFromWKB(), LineStringFromText(), LineStringFromWKB(), MLineFromText(), MLineFromWKB(), MPointFromText(), MPointFromWKB(), MPolyFromText(), MPolyFromWKB(), MultiLineStringFromText(), MultiLineStringFromWKB(), MultiPointFromText(), MultiPointFromWKB(), MultiPolygonFromText(), MultiPolygonFromWKB(), NumGeometries(), NumInteriorRings(), NumPoints(), PointFromText(), PointFromWKB(), PointN(), PolyFromText(), PolyFromWKB(), PolygonFromText(), PolygonFromWKB(), SRID(), StartPoint(), Touches(), X(), Y().
• GLength() is removed in favor of ST_Length().
• The functions described in Section 12.15.4, “Functions That Create Geometry Values from WKB Values” previously accepted either WKB strings or geometry arguments. Geometry arguments are no longer permitted and produce an error. See that section for guidelines for migrating queries away from using geometry arguments.
• The parser no longer treats \N as a synonym for NULL in SQL statements. Use NULL instead. This change does not affect text file import or export operations performed with LOAD DATA
INFILE or SELECT ... INTO OUTFILE, for which NULL continues to be represented by \N. See Section 13.2.7, “LOAD DATA INFILE Syntax”.
• PROCEDURE ANALYSE() syntax is removed.
• The client-side --ssl and --ssl-verify-server-cert options have been removed. Use -- ssl-mode=REQUIRED instead of --ssl=1 or --enable-ssl. Use --ssl-mode=DISABLED instead of --ssl=0, --skip-ssl, or --disable-ssl. Use --ssl-mode=VERIFY_IDENTITY instead of --ssl-verify-server-cert options. (The server-side --ssl option remains unchanged.)
For the C API, MYSQL_OPT_SSL_ENFORCE and MYSQL_OPT_SSL_VERIFY_SERVER_CERT options for mysql_options() correspond to the client-side --ssl and --ssl-verify-server-
cert options and have been removed. Use MYSQL_OPT_SSL_MODE with an option value of
SSL_MODE_REQUIRED or SSL_MODE_VERIFY_IDENTITY instead.
• The --temp-pool server option has been removed.
• The --ignore-builtin-innodb server option and ignore_builtin_innodb system variable have been removed.
• The server no longer performs conversion of pre-MySQL 5.1 database names containing special characters to 5.1 format with the addition of a #mysql50# prefix. Because these conversions are no longer performed, the --fix-db-names and --fix-table-names options for mysqlcheck, the UPGRADE DATA DIRECTORY NAME clause for the ALTER DATABASE statement, and the Com_alter_db_upgrade status variable have been removed.
Upgrades are supported only from one major version to another (for example, 5.0 to 5.1, or 5.1 to 5.5), so there should be little remaining need for conversion of older 5.0 database names to current versions of MySQL. As a workaround, upgrade a MySQL 5.0 installation to MySQL 5.1 before upgrading to a more recent release.
• The mysql_install_db program has been removed from MySQL distributions. Data directory initialization should be performed by invoking mysqld with the --initialize or --initialize- insecure option instead. In addition, the --bootstrap option for mysqld that was used by mysql_install_db has been removed, and the INSTALL_SCRIPTDIR CMake option that controlled the installation location for mysql_install_db has been removed.
• The generic partitioning handler has been removed from the MySQL server. In order to support partitioning of a given table, the storage engine used for the table must now provide its own (“native”) partitioning handler. The --partition and --skip-partition options have been removed
from the MySQL Server, and partitioning-related entries are no longer shown in the output of SHOW PLUGINS or in the INFORMATION_SCHEMA.PLUGINS table.
Two MySQL storage engines currently provide native partitioning support—InnoDB and NDB; of these, only InnoDB is supported in MySQL 8.0. Any attempt to create partitioned tables in MySQL
8.0 using any other storage engine fails.
Ramifications for upgrades. The direct upgrade of a partitioned table using a storage engine other than InnoDB (such as MyISAM) from MySQL 5.7 (or earlier) to MySQL 8.0 is not supported. There are two options for handling such a table:
• Remove the table's partitioning, using ALTER TABLE ... REMOVE PARTITIONING.
• Change the storage engine used for the table to InnoDB, with ALTER TABLE ... ENGINE=INNODB.
At least one of the two operations just listed must be performed for each partitioned non-InnoDB table prior to upgrading the server to MySQL 8.0. Otherwise, such a table cannot be used following the upgrade.
Due to the fact that table creation statements that would result in a partitioned table using a storage engine without partitioning support now fail with an error (ER_CHECK_NOT_IMPLEMENTED), you must make sure that any statements in a dump file (such as that written by mysqldump) from an older version of MySQL that you wish to import into a MySQL 8.0 server that create partitioned tables do not also specify a storage engine such as MyISAM that has no native partitioning handler. You can do this by performing either of the following:
• Remove any references to partitioning from CREATE TABLE statements that use a value for the
STORAGE ENGINE option other than InnoDB.
• Specifying the storage engine as InnoDB, or allow InnoDB to be used as the table's storage engine by default.
For more information, see Section 22.6.2, “Partitioning Limitations Relating to Storage Engines”.
• System and status variable information is no longer maintained in the INFORMATION_SCHEMA. These tables have been removed: GLOBAL_VARIABLES, SESSION_VARIABLES, GLOBAL_STATUS, SESSION_STATUS. Use the corresponding Performance Schema tables instead. See
Section 25.11.13, “Performance Schema System Variable Tables”, and Section 25.11.14, “Performance Schema Status Variable Tables”. In addition, the show_compatibility_56 system variable has been removed. It was used in the transition period during which system and status variable information in INFORMATION_SCHEMA tables was moved to Performance Schema tables, and is no longer needed. These status variables have been removed: Slave_heartbeat_period, Slave_last_heartbeat, Slave_received_heartbeats, Slave_retried_transactions, Slave_running. The information they provided is available in Performance Schema tables; see Migrating to Performance Schema System and Status Variable Tables.
• The Performance Schema setup_timers table has been removed, as has the TICK row in the
performance_timers table.
• The libmysqld embedded server library has been removed, along with:
• The mysql_options() MYSQL_OPT_GUESS_CONNECTION, MYSQL_OPT_USE_EMBEDDED_CONNECTION, MYSQL_OPT_USE_REMOTE_CONNECTION, and MYSQL_SET_CLIENT_IP options
• The mysql_config --libmysqld-libs, --embedded-libs, and --embedded options
• The CMake WITH_EMBEDDED_SERVER, WITH_EMBEDDED_SHARED_LIBRARY, and
INSTALL_SECURE_FILE_PRIV_EMBEDDEDDIR options
• The (undocumented) mysql --server-arg option
• The mysqltest --embedded-server, --server-arg, and --server-file options
• The mysqltest_embedded and mysql_client_test_embedded test programs
• The mysql_plugin utility has been removed. Alternatives include loading plugins at server startup using the --plugin-load or --plugin-load-add option, or at runtime using the INSTALL PLUGIN statement.
• The following server error codes are not used and have been removed. Applications that test specifically for any of these errors should be updated.
• The deprecated INFORMATION_SCHEMA INNODB_LOCKS and INNODB_LOCK_WAITS tables have been removed. Use the Performance Schema data_locks and data_lock_waits tables instead.
Note: In MySQL 5.7, the LOCK_TABLE column in the INNODB_LOCKS table and the
locked_table column in the sys schema innodb_lock_waits and x
$innodb_lock_waits views contain combined schema/table name values. In MySQL 8.0, the data_locks table and the sys schema views contain separate schema name and table name columns. See Section 26.4.3.9, “The innodb_lock_waits and x$innodb_lock_waits Views”.
• InnoDB no longer supports compressed temporary tables. When innodb_strict_mode is enabled (the default), CREATE TEMPORARY TABLE returns an error if ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE is specified. If innodb_strict_mode is disabled, warnings are issued and the temporary table is created using a non-compressed row format.
• InnoDB no longer creates .isl files (InnoDB Symbolic Link files) when creating tablespace data files outside of the MySQL data directory. The innodb_directories option now supports locating tablespace files created outside of the data directory.
With this change, moving a remote tablespace while the server is offline by manually modifying an .isl file is no longer supported. Moving remote tablespace files is now supported by the
innodb_directories option. See Section 15.7.7, “Moving Tablespace Files While the Server is Offline”.
• The following InnoDB file format configuration options were removed:
• innodb_file_format
• innodb_file_format_check
• innodb_file_format_max
• innodb_large_prefix
File format configuration options were necessary for creating tables compatible with earlier versions of InnoDB in MySQL 5.1. Now that MySQL 5.1 has reached the end of its product lifecycle, these options are no longer required.
The FILE_FORMAT column was removed from the INNODB_TABLES and INNODB_TABLESPACES
Information Schema tables.
• The innodb_support_xa system variable, which enables support for two-phase commit in XA transactions, was removed. InnoDB support for two-phase commit in XA transactions is always enabled.
• Support for DTrace has been removed.
• The JSON_APPEND() function has been removed. Use JSON_ARRAY_APPEND() instead.
Options and Variables Deprecated in MySQL 8.0
The following system variables, status variables, and options have been deprecated in MySQL 8.0.
• expire_logs_days: Purge binary logs after this many days. Deprecated as of MySQL 8.0.3.
• innodb_undo_tablespaces: The number of tablespace files that rollback segments are divided between. Deprecated as of MySQL 8.0.4.
• log_syslog: Whether to write error log to syslog. Deprecated as of MySQL 8.0.2.
• symbolic-links: Permit symbolic links for MyISAM tables. Deprecated as of MySQL 8.0.2.
Options and Variables Removed in MySQL 8.0
The following system variables, status variables, and options have been removed in MySQL 8.0.
• Com_alter_db_upgrade: Count of ALTER DATABASE ... UPGRADE DATA DIRECTORY NAME statements. Removed in MySQL 8.0.0.
• Innodb_available_undo_logs: Display the total number of InnoDB rollback segments; different from innodb_rollback_segments, which displays the number of active rollback segments. Removed in MySQL 8.0.2.
• Qcache_free_blocks: Number of free memory blocks in the query cache. Removed in MySQL 8.0.3.
• Qcache_free_memory: The amount of free memory for the query cache. Removed in MySQL 8.0.3.
• Qcache_hits: Number of query cache hits. Removed in MySQL 8.0.3.
• Qcache_inserts: Number of query cache inserts. Removed in MySQL 8.0.3.
• Qcache_lowmem_prunes: Number of queries that were deleted from the query cache due to lack of free memory in the cache. Removed in MySQL 8.0.3.
• Qcache_not_cached: Number of noncached queries (not cacheable, or not cached due to the query_cache_type setting). Removed in MySQL 8.0.3.
• Qcache_queries_in_cache: Number of queries registered in the query cache. Removed in MySQL 8.0.3.
• Qcache_total_blocks: The total number of blocks in the query cache. Removed in MySQL 8.0.3.
• Slave_heartbeat_period: The slave's replication heartbeat interval, in seconds. Removed in MySQL 8.0.1.
• Slave_last_heartbeat: Shows when the latest heartbeat signal was received, in TIMESTAMP format. Removed in MySQL 8.0.1.
• Slave_received_heartbeats: Number of heartbeats received by a replication slave since previous reset. Removed in MySQL 8.0.1.
• Slave_retried_transactions: The total number of times since startup that the replication slave SQL thread has retried transactions. Removed in MySQL 8.0.1.
• Slave_running: The state of this server as a replication slave (slave I/O thread status). Removed in MySQL 8.0.1.
• bootstrap: Used by mysql installation scripts. Removed in MySQL 8.0.0.
• date_format: The DATE format (unused). Removed in MySQL 8.0.3.
• datetime_format: The DATETIME/TIMESTAMP format (unused). Removed in MySQL 8.0.3.
• des-key-file: Load keys for des_encrypt() and des_encrypt from given file. Removed in MySQL 8.0.3.
• group_replication_allow_local_disjoint_gtids_join: Allow the current server to join the group even if it has transactions not present in the group. Removed in MySQL 8.0.4.
• have_crypt: Availability of the crypt() system call. Removed in MySQL 8.0.3.
• ignore-builtin-innodb: Ignore the built-in InnoDB. Removed in MySQL 8.0.3.
• ignore-db-dir: Treat directory as nondatabase directory. Removed in MySQL 8.0.0.
• ignore_db_dirs: Directories treated as nondatabase directories. Removed in MySQL 8.0.0.
• innodb_checksums: Enable InnoDB checksums validation. Removed in MySQL 8.0.0.
• innodb_disable_resize_buffer_pool_debug: Disables resizing of the InnoDB buffer pool. Removed in MySQL 8.0.0.
• innodb_file_format: The format for new InnoDB tables. Removed in MySQL 8.0.0.
• innodb_file_format_check: Whether InnoDB performs file format compatibility checking. Removed in MySQL 8.0.0.
• innodb_file_format_max: The file format tag in the shared tablespace. Removed in MySQL 8.0.0.
• innodb_large_prefix: Enables longer keys for column prefix indexes. Removed in MySQL 8.0.0.
• innodb_locks_unsafe_for_binlog: Force InnoDB not to use next-key locking. Instead use only row-level locking. Removed in MySQL 8.0.0.
• innodb_stats_sample_pages: Number of index pages to sample for index distribution statistics. Removed in MySQL 8.0.0.
• innodb_support_xa: Enable InnoDB support for the XA two-phase commit. Removed in MySQL 8.0.0.
• innodb_undo_logs: Defines the number of undo logs (rollback segments) used by InnoDB; an alias for innodb_rollback_segments. Removed in MySQL 8.0.2.
• log-warnings: Log some noncritical warnings to the log file. Removed in MySQL 8.0.3.
• log_builtin_as_identified_by_password: Whether to log CREATE/ALTER USER, GRANT in backward-compatible fashion. Removed in MySQL 8.0.11.
• log_error_filter_rules: Filter rules for error logging. Removed in MySQL 8.0.4.
• log_syslog: Whether to write error log to syslog. Removed in MySQL 8.0.13.
• log_syslog_facility: Facility for syslog messages. Removed in MySQL 8.0.13.
• log_syslog_include_pid: Whether to include server PID in syslog messages. Removed in MySQL 8.0.13.
• log_syslog_tag: Tag for server identifier in syslog messages. Removed in MySQL 8.0.13.
• max_tmp_tables: Unused. Removed in MySQL 8.0.3.
• metadata_locks_cache_size: Size of the metadata locks cache. Removed in MySQL 8.0.13.
• metadata_locks_hash_instances: Number of metadata lock hashes. Removed in MySQL 8.0.13.
• multi_range_count: The maximum number of ranges to send to a table handler at once during range selects. Removed in MySQL 8.0.3.
• old_passwords: Selects password hashing method for PASSWORD(). Removed in MySQL 8.0.11.
• partition: Enable (or disable) partitioning support. Removed in MySQL 8.0.0.
• query_cache_limit: Do not cache results that are bigger than this. Removed in MySQL 8.0.3.
• query_cache_min_res_unit: Minimal size of unit in which space for results is allocated (last unit will be trimmed after writing all result data). Removed in MySQL 8.0.3.
• query_cache_size: The memory allocated to store results from old queries. Removed in MySQL 8.0.3.
• query_cache_type: Query cache type. Removed in MySQL 8.0.3.
• query_cache_wlock_invalidate: Invalidate queries in query cache on LOCK for write. Removed in MySQL 8.0.3.
• secure-auth: Disallow authentication for accounts that have old (pre-4.1) passwords. Removed in MySQL 8.0.3.
• show_compatibility_56: Compatibility for SHOW STATUS/VARIABLES. Removed in MySQL 8.0.1.
• skip-partition: Do not enable user-defined partitioning. Removed in MySQL 8.0.0.
• sync_frm: Sync .frm to disk on create. Enabled by default. Removed in MySQL 8.0.0.
• temp-pool: Using this option will cause most temporary files created to use a small set of names, rather than a unique name for each new file. Removed in MySQL 8.0.1.
• time_format: The TIME format (unused). Removed in MySQL 8.0.3.
• tx_isolation: The default transaction isolation level. Removed in MySQL 8.0.3.
• tx_read_only: Default transaction access mode. Removed in MySQL 8.0.3.