[
https://issues.apache.org/jira/browse/IGNITE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114528#comment-16114528
]
ASF GitHub Bot commented on IGNITE-5939:
----------------------------------------
Github user isapego closed the pull request at:
https://github.com/apache/ignite/pull/2399
> ODBC: SQLColAttributes should work with legacy attribute codes.
> ---------------------------------------------------------------
>
> Key: IGNITE-5939
> URL: https://issues.apache.org/jira/browse/IGNITE-5939
> Project: Ignite
> Issue Type: Bug
> Components: odbc
> Affects Versions: 2.1
> Reporter: Igor Sapego
> Assignee: Igor Sapego
> Fix For: 2.2
>
>
> According to
> https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlcolattribute-function
>
> {quote}
> The #define values of the ODBC 2.x {{FieldIdentifiers}}
> {{SQL_COLUMN_LENGTH}}, {{SQL_COLUMN_PRECISION}}, and {{SQL_COLUMN_SCALE}} are
> different from the #define values of the ODBC 3.x {{FieldIdentifiers}}
> {{SQL_DESC_PRECISION}}, {{SQL_DESC_SCALE}}, and {{SQL_DESC_LENGTH}}. An ODBC
> 2.x driver need only support the ODBC 2.x values. An ODBC 3.x driver must
> support both "{{SQL_COLUMN}}" and "{{SQL_DESC}}" values for these three
> {{FieldIdentifiers}}. These values are different because precision, scale,
> and length are defined differently in ODBC 3.x than they were in ODBC 2.x.
> {quote}
> Currently, {{SQLColAttributes}} does not work with these three identifiers in
> our driver. Need to be fixed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
