Empty string as value of a parameter results in a space in the stored procedure

Brutus · Post by **Brutus** » Fri 23 Feb 2007 14:29

A stored procedure with the following signature:
PROCEDURE EmptyChar(i_parameter IN CHAR)
called from the client (through OraDirect.net 3.55.18) with an empty string ("") for 'i_parameter', results in an space in the stored procedure.

I expect that the value for 'i_parameter' in the stored procedure, would be 'NULL'.

Alexey · Post by **Alexey** » Thu 01 Mar 2007 08:39

Please send us small test project to reproduce the problem. Include definition of your own database objects.
Use e-mail address provided in the Readme file.
Do not use third party components.

Alexey · Post by **Alexey** » Thu 01 Mar 2007 09:26

We have already reproduced the problem, so you do not have to provide your sample. The bug will be fixed in the next build. Look forward to the announcement on the forum.
Commonly, "" is not acceptable for CHAR fields. You should pass DBNull instead.

Brutus · Post by **Brutus** » Fri 02 Mar 2007 14:46

Thanks in advance for the update.

(Normally DBNull.Value is used to make the code more explicit, but the empty string was used in some 'old' code and the problem occurred during a 1.1-> 2.0 .Net Framework conversion using a newer version of CoreLab.)

Alexey · Post by **Alexey** » Fri 30 Mar 2007 06:02

Have you already tried new build of OraDirect .NET 3.55.20?