Description
If the SQL result set of contains Decimal column it now returns MAX_SHORT as precision and MAX_USHORT as scale, no matter what is the precision and scale of the original table column.
SQL:
create table person(id int, name character(10), age decimal(3,0), primary key (id));
Java (from internal component)
GridQueryFieldMetadata meta = kernal.query().getIndexing().resultMetaData(
"PUBLIC", "select age from person;"
).iterator().next();
assert meta.precision() == 3;
assert meta.scale() == 0;
Attachments
Issue Links
- blocks
-
IGNITE-13801 ODBC: Check ODBC driver with Ab Initio and fix all issues
-
- Resolved
-
- causes
-
IGNITE-16844 Fix IgniteOptimizationAggregationFuncSpec
-
- Resolved
-
- links to
