[
https://issues.apache.org/jira/browse/IGNITE-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443936#comment-16443936
]
Vladimir Ozerov commented on IGNITE-7691:
-----------------------------------------
[~NIzhikov], [~dpavlov], [~tledkov-gridgain],
Folks, this patch is wrong in many places, how come we agreed to merge it?
1) Binary compatibility for thin .NET client is broken - previous version
cannot work with new protocol any more because it doesn't write scale and
precision {{PlatformConfigurationUtils#readQueryEntity}}
2) Binary client docs are not updated (see query entity section -
https://apacheignite.readme.io/docs/binary-client-protocol-cache-configuration-operations)
3) And the most important question - why {{QueryField.precision}} and
{{QueryField.scale}} are not used?
I do not see why we need these fields. Let's just remove them and restore
compatibility ASAP.
> 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.6
>
>
> 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)