[ODBC-66] Support ODBC 3.8 / 4.0 standard Created: 2016-11-15  Updated: 2023-11-08  Resolved: 2023-11-08

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: None
Fix Version/s: 3.2.1

Type: Task Priority: Major
Reporter: Lawrin Novitsky Assignee: Lawrin Novitsky
Resolution: Fixed Votes: 0
Labels: None

Epic Link: Support New ODBC Standards

 Description   

Resources:
https://docs.microsoft.com/en-us/sql/odbc/reference/what-s-new-in-odbc-3-8?view=sql-server-ver15
https://docs.microsoft.com/en-us/sql/odbc/reference/develop-driver/upgrading-a-3-5-driver-to-a-3-8-driver?view=sql-server-ver15



 Comments   
Comment by Lawrin Novitsky [ 2021-04-05 ]

Minimal set of things that have to be done to comply with 3.8
1. Support SQL_OV_ODBC3_80 value for SQL_ATTR_ODBC_VERSION, returning SQL_ERROR for values other than SQL_OV_ODBC2, SQL_OV_ODBC3, and SQL_OV_ODBC3_80. iirc this is even done
2. Driver should return 03.80 from SQLGetInfo for SQL_DRIVER_ODBC_VER info type
3. SQLGEtInfor should return SQL_ASYNC_DBC_NOT_CAPABLE for SQL_ASYNC_DBC_FUNCTIONS info type, i.e. asynchronous operations are not implemented.
4. Support of SQL_ATTR_RESET_CONNECTION connection attribute
5. Streamed output parameters emulation
6 SQLCancelHandle support. iirc this is even done

Comment by Lawrin Novitsky [ 2023-11-08 ]

After re-reading of docs, I've decided, that output parameter streaming is not mandatory. Other items have been added, tests changed/added.
4.0 goes to the separate ticket.

Generated at Thu Feb 08 03:25:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.