Troubleshooting MYSQL or MariaDB Errors from Error 1661 to 1670

SQLServerF1

MariaDB ERROR Code 1661
MySQL SQL State HY000
ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since both row-incapable engines and statement-incapable engines are involved. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1662
MySQL SQL State HY000
ER_BINLOG_ROW_MODE_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = ROW and at least one table uses a storage engine limited to statement-based logging. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1663
MySQL SQL State HY000
ER_BINLOG_UNSAFE_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since statement is unsafe, storage engine is limited to statement-based logging, and BINLOG_FORMAT = MIXED. %s Note: Introduced in 5.5.3.

MariaDB ERROR Code 1664
MySQL SQL State HY000
ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE
Cannot execute statement: impossible to write to binary log since statement is in row format and at least one table uses a storage engine limited to statement-based logging. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1665
MySQL SQL State HY000
ER_BINLOG_STMT_MODE_AND_ROW_ENGINE
Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging.%s Note: Introduced in 5.5.3.
MariaDB ERROR Code 1666
MySQL SQL State HY000
ER_BINLOG_ROW_INJECTION_AND_STMT_MODE
Cannot execute statement: impossible to write to binary log since statement is in row format and BINLOG_FORMAT = STATEMENT. Note: Introduced in 5.5.3.

MariaDB ERROR Code 1667
MySQL SQL State HY000
ER_BINLOG_MULTIPLE_ENGINES _AND_SELF_LOGGING_ENGINE
Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1668
MySQL SQL State HY000
ER_BINLOG_UNSAFE_LIMIT
The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1669
MySQL SQL State HY000
ER_BINLOG_UNSAFE_INSERT_DELAYED
The statement is unsafe because it uses INSERT DELAYED. This is unsafe because the times when rows are inserted cannot be predicted. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1670
MySQL SQL State HY000
ER_BINLOG_UNSAFE_SYSTEM_TABLE
The statement is unsafe because it uses the general log, slow query log, or performance_schema table(s). This is unsafe because system tables may differ on slaves. Note: Introduced in 5.5.3.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1661 to 1670 which performing certain operations against MySQL or MariaDB.

What are MYSQL/MariaDB Errors?

MySQL and MariaDB programs have access to several types of common error information when the server returns an error.

The MYSQL/MariaDB message displayed contains three types of information:
A numeric error code. This number is MySQL-specific and is not portable to other database systems.
A five-character SQLSTATE value. The values are specified by ANSI SQL and ODBC and are more standardized. Not all MySQL error numbers are mapped to SQLSTATE error codes.
A message string that provides a textual description of the error.
When an error occurs, you can access the MySQL error code, the SQLSTATE value, and the message string using C API functions:
MySQL error code: Call mysql_errno()
SQLSTATE value: Call mysql_sqlstate()
Error message: Call mysql_error()

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about MYSQL and MariaDB Error Codes and Error Messages or Warnings on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *