Known problems and workarounds, if any, for SAP Adaptive Server ADO.NET Data Provider versions 2.157 and 4.157.
| CR# | Description |
|---|---|
|
Limitation on precision for decimal and numeric datatypes. Workaround: The Adaptive Server ADO.NET Data Provider currently supports a maximum precision of 26 numbers for a decimal type. The underlying .NET structure and the corresponding Adaptive Server datatypes can handle a higher precision, and attempting to use a precision higher than 26 results in an exception. The Adaptive Server datatypes affected by this limitation are decimal and numeric. |
|
| Change in behavior when datetime parameter is out of
range. Workaround: Previously, when you use Adaptive Server ADO.NET Data Provider, or connect to Adaptive Server version 15.0.x or earlier, and the application binds a datetime parameter to an invalid datetime range, such as 01-01-0001, the Adaptive Server ADO.NET Data Provider returns error 30122, Invalid datetime field. Year is out of range. For Adaptive Server ADO.NET Data Provider that is connected to Adaptive Server 15.7, this behavior has changed. In this case, Adaptive Server ADO.NET Data Provider sends the date to Adaptive Server, and Adaptive Server returns an error. The error code returned is 247, Arithmetic overflow during implicit conversion of BIGDATETIME value 'Jan 1 0001 12:00AM' to a DATETIME field, or something similar. |