You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Igor Sapego (JIRA)" <ji...@apache.org> on 2017/08/04 13:06:00 UTC
[jira] [Created] (IGNITE-5939) ODBC: SQLColAttributes should work
with legacy attribute codes.
Igor Sapego created IGNITE-5939:
-----------------------------------
Summary: 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
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.
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)