Managed Dirver InputOutput Param Issue

Question

Hi!
How do you think, can we treat behavior difference between managed and unmanaged as an issue?
Fake procedure:
PROCEDURE in_out_test( p_some_id number)
is
begin
null;
end;
Sample code:
using System;
using System.Data;
//using Oracle.DataAccess.Client;
using Oracle.ManagedDataAccess.Client;
namespace ManagedODPInOutParamTest
class Program
  static void Main(string[] args)
   Console.WriteLine("go");
   try
    using (var conn = new OracleConnection())
     conn.ConnectionString = "Data Source=vos;User ID=tf2_cust;Password=bla-bla-bla;";
     conn.Open();
     using (var cmd = new OracleCommand("TEST.in_out_test", conn))
      cmd.CommandType = CommandType.StoredProcedure;
      var param = cmd.Parameters.Add("p_some_id", OracleDbType.Decimal, ParameterDirection.InputOutput);
      param.Value = 123456;
      Console.WriteLine("param val befor execute: " + param.Value);
      cmd.ExecuteNonQuery();
      Console.WriteLine("param val after execute: " + param.Value);
     conn.Close();
   catch (Exception ex)
    Console.WriteLine(ex.ToString());
   Console.WriteLine("press");
   Console.ReadLine();
Using Oracle.DataAccess we got:
go
param val befor execute: 123456
param val after execute: 123456
press
Using Oracle.ManagedDataAccess we got:
go
param val befor execute: 123456
param val after execute: null
press
I know that procedure is declared without IN OUT keyword on parameter, but the behavior of managed driver differs from the unmanaged one and this makes them not fully compatible.
Will this be fixed? Or in order to move to managed driver we have to rewrite code, that works fine with unmanaged?
PS: Server version: 11.2.0.3.0, Client version: 12.1.0.1.0, OS: Win7 x64.

Answer 1

And what about this, Alex:
        var cmd = conn.CreateCommand();
        cmd.Parameters.Add("ln", OracleDbType.Varchar2, 32).Value = "aaaaaa";
        cmd.Parameters.Add("dostep", OracleDbType.Byte).Direction = System.Data.ParameterDirection.Output;
        cmd.CommandText = "update uzytkownik set lastlogintime=sysdate,acccnt=acccnt+1 where lower(login_nds)=:ln returning dostep into :dostep";
In użytkownik table there is no record with login_nds == "aaaaaa"
ExecuteNonQuery() crashes with stack:
[ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index]
   System.ThrowHelper.ThrowArgumentOutOfRangeException() +72
   OracleInternal.TTC.Accessors.TTCNumberAccessor.GetByteRepresentation(Int32 currentRow) +28
   OracleInternal.ServiceObjects.OracleParameterImpl.ExtractIntFromAccessor(Accessor accessor, PrmEnumType enumType, OracleDbType oraDbType, Int32 currentRow) +313
   OracleInternal.ServiceObjects.OracleParameterImpl.GetIntFromBytes(Accessor accessor, PrmEnumType enumType, OracleDbType oraDbType) +279
   Oracle.ManagedDataAccess.Client.OracleParameter.PostBind_Int32(Accessor bindAccessor) +259
   OracleInternal.ServiceObjects.OracleCommandImpl.ExtractAccessorValuesIntoParam(OracleParameterCollection paramColl, OracleConnection connection, String commandText, Int64 longFetchSize, Int64 lobFetchSize, Int64[] scnFromExecution) +756
   Oracle.ManagedDataAccess.Client.OracleCommand.ExecuteNonQuery() +504
There was no record selected by a query, so returning clause couldn't return a thing
ODP.NET crashed in this scenario - this is a bug in my opinion
I'm using:
package id="odp.net.managed" version="121.1.1" targetFramework="net40" />