I noticed the following definitions in ODBC headers were inconsistent with what was in the spec:
SQL_ATTR_TYPE_EXCEPTION_BEHAVIOR has four possible values in the spec, SQL_TE_ERROR, SQL_TE_CONTINUE, SQL_TE_REPORT_EXCEPTION and SQL_TE_REPORT_ALL, while there are three defined in sqlext.h which are SQL_TE_ERROR, SQL_TE_CONTINUE and SQL_TE_REPORT.
In sqlext.h the second parameter of SQLNextColumn is named ColumnCount while in the spec it is called Col_or_Param_Num (which seems to make more sense to me).
I assume I should follow what is in the spec and the header will be updated, is that right?
Also, I downloaded the ODBC 4 driver manager and the new ODBCTest from https://github.com/Microsoft/ODBCTest . I suppose they will be updated to work with what is in the spec as well, right?
I noticed the following definitions in ODBC headers were inconsistent with what was in the spec:
SQL_ATTR_TYPE_EXCEPTION_BEHAVIOR
has four possible values in the spec,SQL_TE_ERROR
,SQL_TE_CONTINUE
,SQL_TE_REPORT_EXCEPTION
andSQL_TE_REPORT_ALL
, while there are three defined in sqlext.h which areSQL_TE_ERROR
,SQL_TE_CONTINUE
andSQL_TE_REPORT
.In sqlext.h the second parameter of
SQLNextColumn
is namedColumnCount
while in the spec it is calledCol_or_Param_Num
(which seems to make more sense to me).I assume I should follow what is in the spec and the header will be updated, is that right? Also, I downloaded the ODBC 4 driver manager and the new ODBCTest from https://github.com/Microsoft/ODBCTest . I suppose they will be updated to work with what is in the spec as well, right?