mysql数据库一直显示warning_数据库错误日志中一堆【warning】怎么解决

错误日志中的warning可以不用理会吗？怎么解决这种问题？下面是我的错误日志1611300:33:01[Warning]UnsafestatementwrittentothebinarylogusingstatementformatsinceBINLOG_FORMAT=ST...

错误日志中的warning可以不用理会吗？怎么解决这种问题？下面是我的错误日志161130 0:33:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly. Statement: CREATE PROCEDURE `Escan_overdue`() SQL SECURITY INVOKER call scan_overdue()161130 0:33:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `Escan_overdue`() SQL SECURITY INVOKER call scan_overdue()161130 0:33:01 [Note] Event Scheduler: [root@localhost][fenqi3.Escan_overdue] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.161130 0:33:01 [Note] Event Scheduler: [root@localhost][fenqi3.Escan_overdue] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave.161130 1:33:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly. Statement: CREATE PROCEDURE `Escan_overdue`() SQL SECURITY INVOKER call scan_overdue()161130 1:33:01 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: CREATE PROCEDURE `Escan_overdue`() SQL SECURITY INVOKER call scan_overdue()161130 1:33:01 [Note] Event Scheduler: [root@localhost][fenqi3.Escan_overdue] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column. Inserted values cannot be logged correctly.

展开