Commented by: @cincuranet

You have to specify length of parameter explicitly.

Commented by: Ruben Rorije (rubenrorije)

That is a problem. I can not change the whole user interface to prevent the users to enter too long strings.
Furthermore I have to check my code in all places that the values I use to query the database are not longer than the columns, or in case of expressions, longer than the combined columns.

It seems, but I did not check this extensively, that the value of the parameter will be truncated when the length of the parameter is set.
I think this will result in incorrect results when the value in the parameter is truncated and coincidentally is equal to a value in the database that has the maximum length of the column.

I hope this is not the case, because that will produce the wrong results in my application.

Commented by: Ruben Rorije (rubenrorije)

Because I was not sure, that the behaviour in the new version is not the correct behaviour.
I also checked how, for instance, Sql-server handles the case.
In Sql-server no exception is thrown and no results are returned. Which is exactly what I would like the .Net Data Provider to do.

By the way, I am very much pleased with the .Net DataProvider and this is the first issue I have run into since we are using the .Net dataprovider.

Commented by: @cincuranet

It's not about UI, but about FbParameter.

The value is truncated to size you specify, be it whatever value you feel comfortable. If you look at tracker items, you'll find this behavior was done to align with SqlClient.