Troubleshooting MYSQL or MariaDB Errors from Error 1681 to 1690

SQLServerF1

MariaDB ERROR Code 1681
MySQL SQL State HY000
ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT
‘%s’ is deprecated and will be removed in a future release. Note: Introduced in 5.5.3.
MariaDB ERROR Code 1682
MySQL SQL State HY000
ER_WRONG_NATIVE_TABLE_STRUCTURE
Native table ‘%s’.’%s’ has the wrong structure Note: Introduced in 5.5.3.
MariaDB ERROR Code 1683
MySQL SQL State HY000
ER_WRONG_PERFSCHEMA_USAGE
Invalid performance_schema usage. Note: Introduced in 5.5.3.

MariaDB ERROR Code 1684
MySQL SQL State HY000
ER_WARN_I_S_SKIPPED_TABLE
Table ‘%s’.’%s’ was skipped since its definition is being modified by concurrent DDL statement Note: Introduced in 5.5.3.
MariaDB ERROR Code 1685
MySQL SQL State HY000
ER_INSIDE_TRANSACTION _PREVENTS_SWITCH_BINLOG_DIRECT
Cannot modify @@session.binlog_direct_non_transactional_updates inside a transaction Note: Introduced in 5.5.3.
MariaDB ERROR Code 1686
MySQL SQL State HY000
ER_STORED_FUNCTION_PREVENTS _SWITCH_BINLOG_DIRECT
Cannot change the binlog direct flag inside a stored function or trigger Note: Introduced in 5.5.3.

MariaDB ERROR Code 1687
MySQL SQL State 42000
ER_SPATIAL_MUST_HAVE_GEOM_COL
A SPATIAL index may only contain a geometrical type column Note: Introduced in 5.5.2.
MariaDB ERROR Code 1688
MySQL SQL State HY000
ER_TOO_LONG_INDEX_COMMENT
Comment for index ‘%s’ is too long (max = %lu) Note: Introduced in 5.5.3.
MariaDB ERROR Code 1689
MySQL SQL State HY000
ER_LOCK_ABORTED
Wait on a lock was aborted due to a pending exclusive lock Note: Introduced in 5.5.4.
MariaDB ERROR Code 1690
MySQL SQL State 22003
ER_DATA_OUT_OF_RANGE
%s value is out of range in ‘%s’ Note: Introduced in 5.5.5.

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