MySQL:UnsafestatementwrittentothebinarylogusingstatementformatsinceBINLOG_FORMAT=STATEM

这时我轻轻地闭上了眼睛,我好像来到童话世界,好像在和小鸟讨论秋天的美景,好像在和小草拍秋天的照片。农民伯伯在田野里收获了庄稼,果农们在果园里收获了果子,我们在学校里收获快乐、收获知识、收获成长。

1:错误日志大量错误

150602 14:40:02 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe because the order in which rows are retrieved by the SELECT determines which (if any) rows are updated. This order cannot be predicted and may differ on master and the slave. Statement:INSERT INTO tab_name
  

2:原因:

查了下原因,tab_name 这个表上有2个唯一键。则使用INSERT … ON DUPLICATE KEY UPDATE ,且当前数据库binlog_format是statement格式,这种sql语句就会报unsafe。
  

官方手册:

INSERT … ON DUPLICATE KEY UPDATE statements on tables with multiple primary or unique keys.When executed against a table that contains more than one primary or unique key, this statement is considered unsafe, being sensitive to the order in which the storage engine checks the keys, which is not deterministic, and on which the choice of rows updated by the MySQL Server depends.
  

解决方法:

把binlog_format设置为ROW或者STATEMENT或者修改SQL。

一般情况下就是mysql配置问题,大家可以参考这篇文章://www.haodaima.com/article/84357.htm

到此这篇关于MySQL:UnsafestatementwrittentothebinarylogusingstatementformatsinceBINLOG_FORMAT=STATEM就介绍到这了。要让我写自己的历史,我就写我的错误。更多相关MySQL:UnsafestatementwrittentothebinarylogusingstatementformatsinceBINLOG_FORMAT=STATEM内容请查看相关栏目,小编编辑不易,再次感谢大家的支持!

您可能有感兴趣的文章
centos7安装MySQL教程

MySQL常用SQL查询语句(含复杂SQL查询)

MySQL细数发生索引失效的情况

mysqlenum字段类型的谨慎如何使用

Mysql体系化探讨令人头疼的JOIN运算