0

I constructed a MySqlParameter with MySqlParameter tmp1 = new MySqlParameter("?tmp1", 0.0); and when executing the corresponding insert query received the error message that the respective column cannot be null.

When investigating that parameter in Visual Studio's debugger, its Value property is shown as null, though I think that 0.0 and nullare different things.

Anyway, when I set the value later on with tmp1.Value = 0.0;, the parameter's value is correctly shown as 0. (Note: different values like 1 work correctly in the constructor).

Is that a feature of the constructor of MySqlParameter (MySql.Data.6.9.8, net45) or a bug?

1 Answer 1

0

It is a known bug:

https://bugs.mysql.com/bug.php?id=85027

but comments on that page indicate that some people think of it as a feature...

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.