Troubleshooting MariaDB-specific error codes From Error 1921 to 1932
MariaDB ERROR 1921
Illegal value used as argument of dynamic column function
MariaDB ERROR 1922
Dynamic column contains unknown character set
MariaDB ERROR 1923
At least one of the ‘in_to_exists’ or ‘materialization’ optimizer_switch flags must be ‘on’.
MariaDB ERROR 1924
Query cache is disabled (resize or similar command in progress); repeat this command late
MariaDB ERROR 1925
Query cache is globally disabled and you can’t enable it only for this session
MariaDB ERROR 1926
View ‘%-.192s’.’%-.192s’ ORDER BY clause ignored because there is other ORDER BY clause already.
MariaDB ERROR 1927
Connection was killed
MariaDB ERROR 1928
Internal error: ‘%-.192s’
MariaDB ERROR 1929
Cannot modify @@session.skip_replication inside a transaction
MariaDB ERROR 1930
Cannot modify @@session.skip_replication inside a stored function or trigger
MariaDB ERROR 1931
Query execution was interrupted. The query examined at least %llu rows, which exceeds LIMIT ROWS EXAMINED (%llu). The query result may be incomplete.
MariaDB ERROR 1932
Table ‘%-.192s.%-.192s’ doesn’t exist in engine
Above are list of MariaDB-specific error codes or Error Messages or Warnings from Error 1921 to 1932 received while performing certain operation against MariaDB related products.
What are MariaDB-specific error code Messages?
MariaDB-specific error codes are a set of error codes for use by all MariaDB products. Every MariaDB-specific error message returned by MariaDB, is self explanatory and contains the object name in cases where required.
Hope this was helpful.
Information about MariaDB error code Messages or Warning Messages on Windows and Linux Operating Systems.