Release Notes for Starburst ODBC Driver v3
==========================================

V3 is Starburst's latest ODBC Driver. It is currently available in GA for 
Windows (Intel 32-bits & 64-bits).

Please use the Starburst support portal to submit questions and comments 
including defects. Alternately, you can also direct the same to 
odbc.notify@starburstdata.com. 

Linux and MacOS are currently in private preview. Please contact your 
Starburst rep for details.

Changelog:
---------
* Tue Feb 17 2026 Build System <odbc.notify@starburstdata.com> - 3.2.0
- [O30-472/660/879] Adds support for Microsoft Access' import and linked table features.   
- [O30-902] Adds support for Microsoft Excel.
- [O30-913] Adds support for SQL_DATE, SQL_TIME, and SQL_TIMESTAMP types for improved compatibility with legacy ODBC 2.x applications such as Microsoft Access.
- [O30-985] Adds SQLBindParameter support for SQL_C_DEFAULT so clients that rely on default C-type mappings (including Microsoft Access) can bind parameters successfully.
- [O30-972] Restores server side resource clean-up process when a query is cancelled.
- [O30-608] Corrects SQLColumns & SQLTables bugs that erroneously returned empty results when CatalogName contains SQL wildcard characters.
- [O30-853] Corrects "HYC00 Data type is not supported [typeId=12]" errors when running Power BI RB paginated reports that use placeholder parameters.
- [O30-914] Corrects conversions among date, time, and timestamp types by returning 0 for missing data parts and avoiding the incorrect use of the client system date or time. 
- [O30-992] Corrects SQLDescribeCol & SQLDescribeParam to return the number of fractional-second digits for time-related columns via DecimalDigits, matching ODBC expectations.
- [O30-1021] Corrects SQLTables when IgnoreBrokenCatalog option is not set (default) and SQL_ATTR_METADATA_ID is set to SQL_FALSE (default). Previously, SQLTables fails when CatalogName is %.

* Tue Oct 31 2025 Build System <odbc.notify@starburstdata.com> - 3.1.2
- [O30-878] Implements libcurl debug log
- [O30-885] Updates timezone database to latest as of build time

* Mon Oct 8 2025 Build System <odbc.notify@starburstdata.com> - 3.1.1
- [O30-787] Corrects SQLGetData's handling of StrLen_or_IndPtr to handle long data fetch.
- [O30-873] Corrects crash when closing a statement while a large query is running.
- [O30-880] Restores handling of AutoCommit=true.
- [O30-898] Corrects SQLExecute to escape a bound parameter value.

* Fri Sep 19 2025 Build System <odbc.notify@starburstdata.com> - 3.1.0
- [O30-791] Restores connection string keyword AllowMetadataFromMultipleCatalogs.
- [O30-828] Returns time/timestamp with time zone as local time/timestamp without time zone instead of varchar.

* Wed Sep 15 2025 Build System <odbc.notify@starburstdata.com> - 3.0.15
- [O30-354] Implements SQLSpecialColumns.
- [O30-472] Implements SQL_ATTR_MAX_LENGTH & SQLStatistics.
- [O30-706] Implements SQLNumParams.
- [O30-730] Corrects access violation error in SQLNumResultCols.
- [O30-817] Corrects SQLColAttribute/SQLColAttributes/SQLDescribeCol to return empty catalog/schema/table names.
- [O30-854] Corrects SQLTables/SQLColumns to support Unicode characters in the catalog/schema/table/column name.

* Mon Jul 1 2025 Build System <odbc.notify@starburstdata.com> - 3.0.13
- [O30-744/789/793] Corrects handling of SQL_NUMERIC_STRUCT to use client-specified precision/scale when specified.
- [O30-774] Deprecates MaxDefaultVarcharLength in favor of DefaultVarcharLength.
- [O30-799] Changes CacheOAuthToken defaults to on.
- [O30-800] Deprecates CacheAccessToken in favor of CacheOAuthToken.
- [O30-811] Changes X-Trino-Source header default from "starburst-odbc" to Windows host process name.
Known Limitations:
-----------------
1. Starburst server requires passwords to use ISO-8859-1 (Latin-1) character encoding when using password authentication type. Using characters outside this encoding causes authentication failures when connecting with ODBC. [O30-942]
2. The driver does not support implicit data coercion. A query fails if the bound parameter type (e.g., integer via SQLBindParameter) does not match the destination column type (e.g., varchar). For example, Power BI Report Builder binds parameters as varchar which prevents use of non-varchar parameters.