MySQL 5.6 中的 TIMESTAMP 和 explicit_defaults_for_timestamp 参数

MySQL 5.6 中的中的 TIMESTAMP 和和 explicit_defaults_for_timestamp 参数参数

主要介绍了MySQL 5.6 中的 TIMESTAMP 和 explicit_defaults_for_timestamp 参数,需要的朋友可以参考下

安装MySQL时，有warning:

[root@localhost mysql]# scripts/mysql_install_db --user=mysql

Installing MySQL system tables...2015-08-13 14:20:09 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2015-08-13 14:20:09 0 [Note] ./bin/mysqld (mysqld 5.6.26) starting as process 1934 ...

2015-08-13 14:20:09 1934 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2015-08-13 14:20:09 1934 [Note] InnoDB: The InnoDB memory heap is disabled

2015-08-13 14:20:09 1934 [Note] InnoDB: Completed initialization of buffer pool

2015-08-13 14:20:10 1934 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!

2015-08-13 14:20:10 1934 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB

2015-08-13 14:20:10 1934 [Note] InnoDB: Database physically writes the file full: wait...

2015-08-13 14:20:10 1934 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB

2015-08-13 14:20:11 1934 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB

2015-08-13 14:20:12 1934 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0

2015-08-13 14:20:12 1934 [Warning] InnoDB: New log files created, LSN=45781

2015-08-13 14:20:12 1934 [Note] InnoDB: Doublewrite buffer not found: creating new

2015-08-13 14:20:12 1934 [Note] InnoDB: Doublewrite buffer created

2015-08-13 14:20:12 1934 [Note] InnoDB: 5.6.26 started; log sequence number 0

2015-08-13 14:20:14 1934 [Note] Binlog end

2015-08-13 14:20:14 1934 [Note] InnoDB: FTS optimize thread exiting.

2015-08-13 14:20:14 1934 [Note] InnoDB: Starting shutdown...

2015-08-13 14:20:16 1934 [Note] InnoDB: Shutdown completed; log sequence number 1625977

OK

Filling help tables...2015-08-13 14:20:16 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated.

Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2015-08-13 14:20:16 0 [Note] ./bin/mysqld (mysqld 5.6.26) starting as process 1957 ...

2015-08-13 14:20:16 1957 [Note] InnoDB: Using mutexes to ref count buffer pool pages

2015-08-13 14:20:16 1957 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2015-08-13 14:20:16 1957 [Note] InnoDB: Completed initialization of buffer pool

2015-08-13 14:20:16 1957 [Note] InnoDB: Highest supported file format is Barracuda.

2015-08-13 14:20:16 1957 [Note] InnoDB: 128 rollback segment(s) are active.

2015-08-13 14:20:16 1957 [Note] InnoDB: Waiting for purge to start

2015-08-13 14:20:16 1957 [Note] InnoDB: 5.6.26 started; log sequence number 1625977

2015-08-13 14:20:17 1957 [Note] Binlog end

2015-08-13 14:20:17 1957 [Note] InnoDB: FTS optimize thread exiting.

2015-08-13 14:20:17 1957 [Note] InnoDB: Starting shutdown...

2015-08-13 14:20:18 1957 [Note] InnoDB: Shutdown completed; log sequence number 1625987

./bin/mysqladmin -u root -h localhost.localdomain password 'new-password'

Alternatively you can run:

./bin/mysql_secure_installation

which will also give you the option of removing the test

databases and anonymous user created by default. This is

strongly recommended for production servers.

See the manual for more instructions.

You can start the MySQL daemon with:

cd . ; ./bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl

will be used by default by the server when you start it.

You may edit this file to change server settings

WARNING: Default config file /etc/my.cnf exists on the system

This file will be read by default by the MySQL server

If you do not want to use this, either remove it, or use the

--defaults-file argument to mysqld_safe when starting the server

[root@localhost mysql]#

[Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

其原因是从 5.6开始，timestamp 的默认行为已经是 deprecated 了。