You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2022/07/01 12:25:00 UTC

[jira] [Commented] (IGNITE-17203) SQL API: Implement scale and precision metadata

    [ https://issues.apache.org/jira/browse/IGNITE-17203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561437#comment-17561437 ] 

Andrey Mashenkov commented on IGNITE-17203:
-------------------------------------------

I've jfound we use Short.MAX_VALUE as max precision and scale for numeric types.
AFAIK, decimal in .NET is limited with 38 digits.

What is a use case that requires support for such large values? 

> SQL API: Implement scale and precision metadata
> -----------------------------------------------
>
>                 Key: IGNITE-17203
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17203
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Pavel Tupitsyn
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha6
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> *scale()* and *precision()* in *ColumnMetadata* interface return incorrect values. Implement them properly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)