Problem with out parameter / oracle and direct=false.

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
Posts: 5
Joined: Tue 05 Oct 2010 08:35
Location: -1

Problem with out parameter / oracle and direct=false.

Post by andrelau » Mon 17 Oct 2011 12:22

here's the problem.

We mapped a stored procedure and we recently noticed (upgrading to 6.x) that when we call it using 'Direct mode = false', string in the output parameter ends with spaces plus one zero and trim doesn’t work. (creates a bug in our software as we are expecting 11 char after trim.

If we switch to “direct = true” in the config file, it’s ok (string ends with spaces, no ‘zero’ byte’ and trim works.


The setup.
• Oracle windows client
• Devart 6.50.228 (same with 6.10) - was working with 5.6+

We call a stored proc inside a package.

Here’s the Oracle Part.

Code: Select all

SUBTYPE st_myparameter IS MyTable.Field%TYPE;
(field is declared as Char(11))

Code: Select all

PROCEDURE MyProcedure(
                                  Arg1    IN     st_myparameter,
                                  Arg2   IN     st_anothersubtype,
                                  arg_o_1       OUT st_myparameter,
                                  arg_o_codret       OUT integer
Here’s the .Net part.

In the Model.designer.cs we can find this after the Import.

Code: Select all

public int MyProcedure (global::System.String Arg1, global::System.String Arg2, ObjectParameter arg_o_1, ObjectParameter aRG_O_CODRET)
Q1 : As output subtype should be char(11) is it logical to get a very long string in the arg_o_1 ?
I mean we expect a 11 char string and what we get is 2000 chars long !

Q2: When we use Direct = true the last char of the 2000 is a space. Trim is working fine.
When we use Direct = false , last char is zero and thus, the trim doesn’t work.

Posts: 5
Joined: Tue 05 Oct 2010 08:35
Location: -1

Post by andrelau » Tue 18 Oct 2011 09:40


Devart Team
Posts: 8034
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Fri 21 Oct 2011 10:27

We cannot reproduce the problem with dotConnect for Oracle v 6.50.228 basing on the description of the issue above. Please send us a small complete test project with the DDL/DML script of the corresponding database objects.

Post Reply