安装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: Mutexes and rw_locks use InnoDB's own implementation

2015-08-13 14:20:09 1934 [Note] InnoDB: Memory barrier is not used

2015-08-13 14:20:09 1934 [Note] InnoDB: Compressed tables use zlib 1.2.3

2015-08-13 14:20:09 1934 [Note] InnoDB: Using Linux native AIO

2015-08-13 14:20:09 1934 [Note] InnoDB: Not using CPU crc32 instructions

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

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: 128 rollback segment(s) are active.

2015-08-13 14:20:12 1934 [Warning] InnoDB: Creating foreign key constraint system tables.

2015-08-13 14:20:12 1934 [Note] InnoDB: Foreign key constraint system tables created

2015-08-13 14:20:12 1934 [Note] InnoDB: Creating tablespace and datafile system tables.

2015-08-13 14:20:12 1934 [Note] InnoDB: Tablespace and datafile system tables created.

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

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: The InnoDB memory heap is disabled

2015-08-13 14:20:16 1957 [Note] InnoDB: Mutexes and rw_locks use InnoDB's own implementation

2015-08-13 14:20:16 1957 [Note] InnoDB: Memory barrier is not used

2015-08-13 14:20:16 1957 [Note] InnoDB: Compressed tables use zlib 1.2.3

2015-08-13 14:20:16 1957 [Note] InnoDB: Using Linux native AIO

2015-08-13 14:20:16 1957 [Note] InnoDB: Not using CPU crc32 instructions

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

OK

To start mysqld at boot time you have to copy

support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !

To do so, start the server, then issue the following commands:

  ./bin/mysqladmin -u root password 'new-password'

  ./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

  cd mysql-test ; perl mysql-test-run.pl

Please report any problems at http://bugs.mysql.com/

The latest information about MySQL is available on the web at

  http://www.mysql.com

Support MySQL by buying support/licenses at http://shop.mysql.com

New default config file was created as ./my.cnf and

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 了。

在MySQL 5.6.6之前，TIMESTAMP的默认行为：

  • TIMESTAMP列如果没有明确声明NULL属性，默认为NOT NULL。（而其他数据类型，如果没有显示声明为NOT NULL，则允许NULL值。）设置TIMESTAMP的列值为NULL，会自动存储为当前timestamp。
  • 表中的第一个TIMESTAMP列，如果没有声明NULL属性、DEFAULT或者 ON UPDATE，会自动分配 DEFAULT CURRENT_TIMESTAMP和ON UPDATE CURRENT_TIMESTAMP 属性。
  • 表中第二个TIMESTAMP列，如果没有声明为NULL或者DEFAULT子句，默认自动分配’0000-00-00 00:00:00′。插入行时没有指明改列的值，该列默认分配’0000-00-00 00:00:00′，且没有警告。

要关闭警告，需要加入下面的参数：

[mysqld]

explicit_defaults_for_timestamp=true

重启MySQL后错误消失，这时TIMESTAMP的行为如下：

  • TIMESTAMP如果没有显示声明NOT NULL，是允许NULL值的，可以直接设置改列为NULL，而没有默认填充行为。
  • TIMESTAMP不会默认分配DEFAULT CURRENT_TIMESTAMP 和 ON UPDATE CURRENT_TIMESTAMP属性。
  • 声明为NOT NULL且没有默认子句的TIMESTAMP列是没有默认值的。往数据表中插入列，又没有给TIMESTAMP列赋值时，如果是严格SQL模式，会抛出一 个错误，如果严格SQL模式没有启用，该列会赋值为’0000-00-00 00:00:00′，同时出现一个警告。（这和MySQL处理其他时间类型数据一样，如DATETIME）
    （参见：http://www.williamsang.com/archives/818.html）

也就是 explicit_defaults_for_timestamp 关闭了 timestamp 类型字段锁拥有的一些会让人感到奇怪的默认行为，加入了该参数之后，如果还需要为 timestamp类型的字段指定默认行为，那么就需要显示的在创建表时显示的指定。explicit_defaults_for_timestamp 也就是这个意思：显示指定默认值为timestamp类型的字段。

MySQL 5.6 中的 TIMESTAMP 和 explicit_defaults_for_timestamp 参数的更多相关文章

  1. MySQL中有关TIMESTAMP和DATETIME的总结

    一.MySQL中如何表示当前时间? 其实,表达方式还是蛮多的,汇总如下: CURRENT_TIMESTAMP CURRENT_TIMESTAMP() NOW() LOCALTIME LOCALTIME ...

  2. mysql 5.6 中 explicit_defaults_for_timestamp参数

    mysql 5.6 中 explicit_defaults_for_timestamp参数 一: 官方文档中关于explicit_defaults_for_timestamp参数说明如下: expli ...

  3. MySQL字符类型datetime与timestamp

    这片博客来详细分区一下这哥俩! 首先来说明这两个字符类型: DATETIME 8 1000-01-01 00:00:00 ~9999~12-31 23:59:59 0000-00-00 00:00:0 ...

  4. mysql explicit_defaults_for_timestamp参数

    在mysql中:- timestamp列如果没有显式定义为null,默认会被设置为not null属性.(其它的数据类型如果没有显式定义为not null,默认是可以为null的).设置timesta ...

  5. 【MySQL】explicit_defaults_for_timestamp 参数详解

    简介:explicit_defaults_for_timestamp 系统变量决定MySQL服务端对timestamp列中的默认值和NULL值的不同处理方法. 此变量自MySQL 5.6.6 版本引入 ...

  6. mysql error 1067 invalid default timestamp

    问题 MySQL 5.7版本,在创建数据表时,使用以下语句定义一个字段: `update_time` timestamp DEFAULT '0000-00-00 00:00:00' ON UPDATE ...

  7. 涂抹mysql笔记-数据库中的权限体系

    涂抹mysql笔记-数据库中的权限体系<>能不能连接,主机名是否匹配.登陆使用的用户名和密码是否正确.mysql验证用户需要检查3项值:用户名.密码和主机来源(user.password. ...

  8. 将Hive统计分析结果导入到MySQL数据库表中（一）——Sqoop导入方式

    https://blog.csdn.net/niityzu/article/details/45190787 交通流的数据分析,需求是对于海量的城市交通数据,需要使用MapReduce清洗后导入到HB ...

  9. MAC下 mysql不能插入中文和中文乱码的问题总结

    MAC下 mysql不能插入中文和中文乱码的问题总结 前言 本文中所提到的问题解决方案,都是基于mac环境下的,但其他环境,比如windows应该也适用. 问题描述 本文解决下边两个问题: 往mysq ...

随机推荐

  1. attachEvent和addEventListener区别

    一般来说,可以直接封装成这种形式: var addEvent = function(element,type,handler){ if(element.addEventListener){ //DOM ...

  2. Unity实现滑页效果（UGUI）

    简介 项目需要...直接展示效果吧: 原理 使用UGUI提供的ScrollRect和ScrollBar组件实现基本滑动以及自己控制每次移动一页来达到滑页的效果. 实现过程 1.创建两个panel,上面 ...

  3. C#中override和new修饰符的区别

    (new)“隐藏”,(override)“覆盖”(重写).不过要弄清楚这两个有什么区别确实也很难,因为子类在使用父类方法时根本看不出区别,子类不管父类是new了还是override了,用的都是父类方法 ...

  4. TreeBuilder科学的树创建器

    public static class TreeBuilder { public static List<dynamic> Build(IEnumerable<dynamic> ...

  5. python函数和常用模块（一）,Day3

    set集合 函数 三元运算 lambda表达式 内置函数1 文件操作 set集合 创建 se = {"123", "456"} # 直接创建一个集合 se = ...

  6. ASP.NET Core 1.0开发Web API程序

    .NET Core版本:1.0.0-rc2Visual Studio版本:Microsoft Visual Studio Community 2015 Update 2开发及运行平台:Windows ...

  7. RabbitMQ与AMQP协议详解

    1. 消息队列的历史 了解一件事情的来龙去脉,将不会对它感到神秘.让我们来看看消息队列(Message Queue)这项技术的发展历史. Message Queue的需求由来已久,80年代最早在金融交 ...

  8. ssh 客户端远程vi文本文件中文乱码（亲测）

    由于是生产环境,且非笔者控制,为了避免影响系统全局,仅对本session有效 export LANG="zh_CN.UTF-8"export LANG="zh_CN.GB ...

  9. Linux初学者指南

    1.为啥我们要学习Linux? 我们干嘛要学习Linux? Linux能给我们带来什么价值呢? Linux给我的感觉就是稳定,免费,性能好. 稳定,体现在哪里?我们使用PC机,安装的操作系统一般是wi ...

  10. TSQL生成Combguid

    Nhibernate实现combguid /// <summary> /// Generate a new <see cref="Guid"/> using ...