MySQL ignores SET SQL_LOG_UPDATE because the update log is obsolete and replaced by the binary log.
MySQL Error 1315: ER_UPDATE_LOG_DEPRECATED_IGNORED appears when a session executes SET SQL_LOG_UPDATE. The statement is ignored because the legacy update log was removed after MySQL 5.0 in favor of the binary log. Remove or replace the deprecated command to resolve the warning.
The update log is deprecated and replaced by the binary
MySQL issues this warning (error code 1315, SQLSTATE 42000) when a client executes SET SQL_LOG_UPDATE. The directive once enabled the update log, but that log was removed in MySQL 5.0. Instead, MySQL relies on the binary log for replication and point-in-time recovery.
The server therefore ignores the request and returns ER_UPDATE_LOG_DEPRECATED_IGNORED. Although classified as a warning, the message may break automation scripts that check for a clean result set or rely on the update log behavior.
The error appears during session initialization scripts, legacy application code, or stored routines that still issue SET SQL_LOG_UPDATE. It can also surface after a MySQL upgrade if outdated configuration snippets were not cleaned up.
Leaving deprecated commands in code reduces clarity, clutters logs, and can hide truly critical errors. Removing SET SQL_LOG_UPDATE ensures forward compatibility with newer MySQL versions and simplifies replication troubleshooting.
Old shell or application startup scripts often contained SET SQL_LOG_UPDATE to toggle the now-removed update log.
Early ORM versions for PHP and Perl emitted SET SQL_LOG_UPDATE before each write transaction and were never patched.
Developers sometimes paste historical examples into modern sessions without realizing the directive is obsolete.
A MySQL upgrade may leave deprecated parameters in my.cnf or stored procedures that no longer serve any purpose.
Raised when binary logging is disabled but required for a statement. Unlike 1315, this stops execution.
Appears when attempting to access an obsolete log file defined in my.cnf.
Occurs when a trigger references a view or temp table that cannot be logged properly in the binary log.
No. It is a warning. The affected statement still runs, but the directive is ignored.
Yes. Start MySQL with log_error_verbosity=2 or use SHOW WARNINGS if you only need to filter programmatically.
No. Replication now relies exclusively on the binary log, which is independent of the deprecated update log.
Galaxy’s linter detects deprecated MySQL syntax and proposes auto-fixes, preventing the warning from appearing in shared queries.
.avif)
.avif){kind=logo}
