Troubleshooting MYSQL or MariaDB Errors from Error 1691 to 1700

SQLServerF1

MariaDB ERROR Code 1691
MySQL SQL State HY000
ER_WRONG_SPVAR_TYPE_IN_LIMIT
A variable of a non-integer based type in LIMIT clause Note: Introduced in 5.5.5.
MariaDB ERROR Code 1692
MySQL SQL State HY000
ER_BINLOG_UNSAFE_MULTIPLE_ENGINES _AND_SELF_LOGGING_ENGINE
Mixing self-logging and non-self-logging engines in a statement is unsafe. Note: Introduced in 5.5.5.
MariaDB ERROR Code 1693
MySQL SQL State HY000
ER_BINLOG_UNSAFE_MIXED_STATEMENT
Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them. Note: Introduced in 5.5.5.

MariaDB ERROR Code 1694
MySQL SQL State HY000
ER_INSIDE_TRANSACTION_ PREVENTS_SWITCH_SQL_LOG_BIN
Cannot modify @@session.sql_log_bin inside a transaction Note: Introduced in 5.5.5.
MariaDB ERROR Code 1695
MySQL SQL State HY000
ER_STORED_FUNCTION_ PREVENTS_SWITCH_SQL_LOG_BIN
Cannot change the sql_log_bin inside a stored function or trigger Note: Introduced in 5.5.5.
MariaDB ERROR Code 1696
MySQL SQL State HY000
ER_FAILED_READ_FROM_PAR_FILE
Failed to read from the .par file Note: Introduced in 5.5.5.

MariaDB ERROR Code 1697
MySQL SQL State HY000
ER_VALUES_IS_NOT_INT_TYPE_ERROR VALUES
value for partition ‘%s’ must have type INT Note: Introduced in 5.5.7.
MariaDB ERROR Code 1698
MySQL SQL State 28000
ER_ACCESS_DENIED_NO_PASSWORD_ERROR
Access denied for user ‘%s’@’%s’ Note: Introduced in 5.5.7.
MariaDB ERROR Code 1699
MySQL SQL State HY000
ER_SET_PASSWORD_AUTH_PLUGIN
SET PASSWORD has no significance for users authenticating via plugins Note: Introduced in 5.5.7.
MariaDB ERROR Code 1700
MySQL SQL State HY000
ER_GRANT_PLUGIN_USER_EXISTS
GRANT with IDENTIFIED WITH is illegal because the user %-.*s already exists Note: Introduced in 5.5.7.

Above are the list of shared MySQL and MariaDB Error Codes and their Description including SQL state and exact error code from Error 1691 to 1700 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 *