Shulou(Shulou.com)05/31 Report--

This article mainly introduces "how to solve the Warning problem of mysql". In the daily operation, I believe many people have doubts about how to solve the Warning problem of mysql. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubt of "how to solve the Warning problem of mysql"! Next, please follow the editor to study!

The error log of restarting mysql today shows the following warning:

2016-06-24 09:20:07 0 [Warning] option 'general_log': boolean value' / data/DB/mysql/select.log' wasn't recognized. Set to OFF.

2016-06-24 09:20:07 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use-explicit_defaults_for_timestamp server option (see documentation for more details).

The first warning is that the query log file was not found, and the system chose to turn off the query log function:

[root@trcloud-gtt-dw] # ls-l / data/DB/mysql/select.log

Ls: cannot access / data/DB/mysql/select.log: No such file or directory

[root@trcloud-gtt-dw ~] # touch / data/DB/mysql/select.log

[root@trcloud-gtt-dw ~] # chown mysql:mysql / data/DB/mysql/select.log

Solve by creating a file

The second warning is to turn off this non-standard behavior by turning on the system variable explicit_defaults_for_timestamp before starting the service! In this way, the system can process the timestamp as follows:

Timestamp olives that are not explicitly declared as not null will allow null values. If set to null, it will be null, not the current timestamp!

No timestamp olive is automatically assigned to default current_timestamp or on update current_timestamp. It's about explicitly assigning values!

Timestamp Lam is declared as not null and does not explicitly declare a default value will be determined to have no default value. Inserting a record into such an olive will completely depend on the mood of SQL mode. If it is strict mode, report an error!

If not, it will be assigned a value of'00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 and give a warning. It's the same with DATETIME!

Solve the problem by adding explicit_defaults_for_timestamp=true under mysql.cnf,mysqld

At this point, the study on "how to solve the Warning problem of mysql" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.