Oracle.ManagedDataAccess.Types.OracleDecimal.Value returns corrupted value after SetPrecision

dunkan

Hello!

I have found that OracleDecimal lost last digits of an integer value after the SetPrecision method call.

The following test doesn't pass for Oracle.ManagedDataAccess 4.122.1.0 and Oracle.ManagedDataAccess.Core.2.12.0-beta2:

OracleDecimal o5 = new OracleDecimal(10304927536231884057971014491M);OracleDecimal fo5 = OracleDecimal.SetPrecision(o5, 28);decimal fd5 = fo5.Value;Debug.Assert(fd5.ToString() == fo5.ToString());  // fd5 == 1030492753623188405797101449// fo5 == 10304927536231884057971014490

But the same code is ok for Oracle.DataAccess 4.122.1.0.

It seems to be a bug in the Oracle.ManagedDataAccess implementation.

Alex Keh-Oracle

I was able to reproduce the error using your sample code. I have filed bug 27815019, which should be fixed first in managed ODP.NET, then ODP.NET Core.

Alex Keh-Oracle

I was able to reproduce the error using your sample code. I have filed bug 27815019, which should be fixed first in managed ODP.NET, then ODP.NET Core.