Bug spider log is using unsafe statement?

hopefully my thread doesnt get deleted this time


i am getting thousands of these entries into the syslog on a mariadb nginx server.

could you advise where to modify this code to stop the error.

Apr 13 06:38:53 srv1 mysqld: 150413 6:38:53 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement$
Apr 13 06:38:53 srv1 mysqld: #011#011#011SET spiderhits = spiderhits + 1#015
Apr 13 06:38:53 srv1 mysqld: #011#011#011ORDER BY sitemapbuildlogid DESC LIMIT 1

It's safe to ignore these warnings

What it means is that the query we run can have unpredictable results, but not in the way we use it, so it's fine

it means replication may not work. the advised method to use is mixed not statement.

also as i am getting approx 3-4 entries per second from this its a bit difficult to ignore it.

can you not modify the statement to mixed so it doesnt cause the errors?

https://mariadb.com/kb/en/mariadb/unsafe-statements-for-replication/

I'll make some changes to the next version

If this continues to be an issue post Monday's update, please start a new support ticket with the updated information. Thanks!