I found that in my project order of named parameter has sense.
I call this procedure
CREATE PROCEDURE `test`.`TestProc` (
in myText varchar (5),
in myText2 varchar (100)
)
BEGIN
END
If I add parameters like this:
command.CommandText = "testProc";
command.CommandType = System.Data.CommandType.StoredProcedure;
command.Parameters.AddWithValue("myText2", "aaaaaaaaaaaaaaaaa");
command.Parameters.AddWithValue("myText", "bbbb");
I get "Data too long" exception. Also I can't reproduce this in test project.
Any thoughts?
I found the cause. Looks like bug in MySql .Nat Data Provider. To reproduce the bug you need to call this not under the root user.
Conclusion: MySql.Data version 6.2.3.0. Order of named parameter has sense If you call procedure with non root db account