[
https://issues.apache.org/jira/browse/IGNITE-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16430507#comment-16430507
]
Taras Ledkov commented on IGNITE-7691:
--------------------------------------
[~NIzhikov], [~vozerov], the patch looks good.
But I have one question:
The implementation looks like stub. Why we need this implementation?
In common SQL servers fixed precision specify the column's store format and
default column output.
At the proposal implementation:
{code}
CREATE TABLE TEST (id INT, val DECIMAL(2,1));
INSERT INTO TEST (1, 123456789);
INSERT INTO TEST (2, 12345678.12345678);
INSERT INTO TEST (3, .123456789);
SELECT * from TEST;
// Result is:
1, 123456789
2, 12345678.12345678
3, 0.123456789
// For specified precision and scale it is MUST BE:
1, 9.9
2, 9.9
3, 0.1
{code}
Please clarify the main goal of the patch.
I'm afraid that the user may be confused the contradiction between right CREATE
TABLE syntax (and right metadata) and wrong query results.
> Provide info about DECIMAL column scale and precision
> -----------------------------------------------------
>
> Key: IGNITE-7691
> URL: https://issues.apache.org/jira/browse/IGNITE-7691
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.4
> Reporter: Nikolay Izhikov
> Assignee: Nikolay Izhikov
> Priority: Minor
> Fix For: 2.5
>
>
> Currently, it impossible to obtain scale and precision of DECIMAL column from
> sql table metadata.
> Ignite should provide those type of meta information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
