Tags: trinodb/trino-odbc
Tags
BUG: System DSNs decryptable by system users (#24) One feature blocking the ODBC driver from working on the Power BI Gateway server was that System DSNs were usable by anyone on the system, but the client secret decryption was only possible by the user who created the DSN. This meant that when the Power BI Gateway Server tried to use the DSN via its service account, the client secret could not be decrypted. With this commit in place, I have observed queries running via the Power BI Gateway server both for on-demand as well as scheduled data refreshes.
SQLColumns handle timestamp with time zone (#15) Handle type code 2014 in SQLColumns - it appears to be a proprietary extension to trino that works with trino's JDBC driver. In the world of ODBC, the closest we can come is to a regular timestamp which is type code 93.
Fix external auth refresh for long queries. (#2) When running queries that do not exceed the expiration of the access token but are within the refresh grace period, make sure to remove the "Authorization" header from CURL before reauthenticating. It's still valid during the grace period, but we want to trigger a re-auth intentionally. Also fixed whitespace and PR workflow issues - growing pains from moving the project to public github.