Closed jduo closed 7 years ago
It's fine for drivers to expose these as custom columns in pre-ODBC 4.0 environments, but clients can't assume the semantics of these columns until 4.0.
Added the ability to support new columns without reporting 4.x in catalog functions to section 5.2, ODBC 3.x Drivers.
Under SQLColumns, there are several new columns added when running an ODBC 4.0 environment. Can these columns also be exposed in other ODBC versions, and just get treated as custom columns in those cases?