Error
Error Code:
1210
MariaDB Error 1210: Invalid Function Arguments
Description
Error 1210, "Incorrect arguments to %s", indicates that a function, stored procedure, or command was invoked with parameters that do not satisfy its expected signature. This typically occurs when the number, data type, or value of the arguments provided do not align with the requirements of the called routine.
Error Message
Incorrect arguments to %s
Known Causes
3 known causesMismatched Argument Count
A function or procedure was called with an incorrect number of arguments (either too many or too few) compared to what it is designed to accept.
Incorrect Argument Data Type
One or more arguments provided do not match the expected data type for their respective parameters (e.g., passing a string where an integer is required).
Argument Value Out of Range
An argument's value, though of the correct type, falls outside the acceptable range or is not a valid option for the specific parameter.
Solutions
3 solutions available1. Verify Function Name and Syntax easy
Ensure the function name is spelled correctly and used with the right number/type of arguments.
1
Review the SQL statement where the error occurs. Carefully check the spelling of the function being called. Refer to the MariaDB documentation for the correct function name and its expected arguments.
SELECT YOUR_FUNCTION(argument1, argument2, ...);
-- Example of a common mistake:
-- SELECT SUBSTRING(column_name, start_position) -- Missing length argument for SUBSTRING
-- Correct usage for SUBSTRING:
SELECT SUBSTRING(column_name, start_position, length);2
Count the number of arguments passed to the function and compare it with the function's definition in the MariaDB documentation. Ensure each argument's data type is compatible with what the function expects.
SELECT DATE_FORMAT(your_date_column, '%Y-%m-%d'); -- Correct for a single argument
-- SELECT DATE_FORMAT(your_date_column, '%Y-%m-%d', 'America/New_York'); -- Incorrect, DATE_FORMAT expects only two arguments2. Check for User-Defined Function (UDF) Issues medium
If using a UDF, verify its definition, compilation, and registration in MariaDB.
1
If the error originates from a user-defined function (UDF), examine the UDF's source code. Ensure the function signature in the code matches how it's registered with MariaDB.
-- Example of C UDF signature:
my_udf_function(MYSQL_FUNCTIONS *mysql_funcs, char *args, ...)
-- Corresponding registration in MariaDB:
-- CREATE FUNCTION my_udf_function RETURNS STRING SONAME 'your_udf.so';2
Verify that the UDF shared object (.so file) is correctly placed in MariaDB's plugin directory and that MariaDB has the necessary permissions to access it.
SHOW VARIABLES LIKE 'plugin_dir'; -- Find your plugin directory
-- Ensure your_udf.so is present in the output directory.3
Recompile the UDF source code if any changes were made, ensuring no compilation errors occur. Reload or restart the MariaDB server if necessary after placing the updated UDF.
gcc -shared -o your_udf.so your_udf.c -I/usr/include/mysql3. Validate Data Types of Arguments medium
Ensure that the data types of values passed to the function are appropriate.
1
Inspect the data types of the columns or literal values being passed as arguments to the function. MariaDB functions often have strict data type requirements. Implicit type conversions might not always work as expected.
SELECT COUNT(column_name) FROM your_table WHERE your_function(column_name) = 'some_value';
-- If 'column_name' is a string and 'your_function' expects a number, this can cause an error.
-- Use explicit casting if necessary:
SELECT COUNT(column_name) FROM your_table WHERE your_function(CAST(column_name AS UNSIGNED)) = 'some_value';2
Use `DESCRIBE your_table;` or `SHOW CREATE TABLE your_table;` to confirm the data types of your table columns.
DESCRIBE your_table;