Amazon Redshift ODBC Driver 1.3.6

Transcription

1 Amazon Redshift ODBC Driver Released August 10, 2017 These release notes provide details of enhancements, features, and known issues in Amazon Redshift ODBC Driver 1.3.6, as well as the version history. NOTE: Please be aware that Linux system requirements have changed as of this release. Please see the Installation and Configuration Guide for more details. Enhancements & New Features Support for Federated Authentication with Single Sign-On The driver now supports IAM authentication, and federated authentication through AD FS, PingFederate, and Okta Identity Providers. Enhanced Support for Viewing External Redshift Spectrum Tables The driver now supports external tables in Amazon Redshift Spectrum. Redesigned DSN dialog box on Windows platforms The DSN configuration dialog box has been refreshed on Windows to provide a better user experience. Changed default SSL mode The default SSL mode is now verify-ca, and the driver now includes the required CA root certificate for SSL verification. DSN option to disable concurrent ODBC statements The driver provides the DSN key EnforceSingleStatement to disable creation of multiple concurrent ODBC statements. This feature is deactivated by default. Support for SQL_ATTR_CONNECTION_DEAD The driver now supports this standard ODBC connection attribute that checks whether there is still an active connection to the data source. 1

2 Window Trust Store supported The driver can be configured to verify the server identity using SSL certificates stored in the Windows Trust Store. The following issues have been resolved in Amazon Redshift ODBC Driver Error when attempting to save DSN from an account without administrative privileges in Windows. Cannot update timestamp columns in MS Access. The driver now maps timestamp columns to the correct ODBC 2 type in ODBC 2 environments. Access violation when running multiple concurrent statements under the same ODBC connection. Version History Version Released November 16, 2016 Enhancements & New Features Updated encryption options for user credentials The Windows driver now supports encryption methods that are specific to User DSNs and System DSNs. You can configure the Encrypt Password option so that credentials can only be used by the current Windows user (recommended for User DSNs) or used by all users on the same machine (recommended for System DSNs). CONVERT function now supported You can now use the ODBC CONVERT scalar function to convert data to a specific data type. New location for SSL certificates During SSL verification, the driver now reads certificates from the lib subfolder in the driver installation directory. Previously, the driver read certificates from the 2

3 %APPDATA%\postgresql\ directory on Windows machines and the ~/.postgresql/ directory on non-windows machines. TIMESTAMPADD function now supported You can now use the TIMESTAMPADD datetime scalar function. Enhanced driver security A new security model has been implemented to further improve the driver's industry-standard security protocol. SQLNativeSql function now supported You can now use the SQLNativeSql function to translate a query from standard SQL to native SQL. Column names now based on detected ODBC API version The driver now automatically detects the ODBC API version that is being used in the application, and returns correct column names for ODBC catalog functions based on the ODBC API version. Updated error codes The driver now returns the corresponding SQL State error codes for errors, simplifying the process of identifying and resolving errors. Custom SSL certificate name and path You can now specify a custom SSL certificate name and location. The following issues have been resolved in Amazon Redshift ODBC Driver OSX installer shows errors when installing on OSX El Capitan. Unable to retrieve location of error messages on OSX and Linux. In some cases, the SingleRowMode and TCP keepalives settings do not work when they are set in the odbc.ini file. Driver returns incorrect data types when SQLGetTypeInfo is called. When parameters are used as arguments to certain scalar functions, an error occurs. 3

4 In some cases, the name of the INI file for driver-wide configuration settings ([vendor].redshiftodbc.ini or [vendor].amazonredshiftodbc.ini) does not contain the correct vendor name. After setting the AMAZONREDSHIFTODBCINI environment variable, the driver does not use the specified amazon.redshiftodbc.ini configuration file. When executing a query that contains bound parameters, the driver returns incorrect column type information. When calling SQLGetTypeInfo, the driver erroneously returns TIME as a supported data type. In some cases, when calling ODBC escape functions that do not contain parentheses (for example, {fn CURRENT_TIME}) or are formatted incorrectly, an access violation occurs. In some cases, after executing a query directly and retrieving all the data, the driver returns incorrect results for the next query that is executed. Redshift ODBC returns HY000 for all errors. When using parameterized queries in Declare-Fetch mode, the driver does not sanitize inputs. Queries with columns that reference only parameters produce assertion failures. Incomplete parameter SqlTypeMetadata handling under Declare-Fetch mode. Potential instability when handling invalid network inputs. Null terminated string parameter is not bound correctly. Escape Interval not handled correctly. Data that is converted to timestamps with milliseconds may scale incorrectly. Conversion from valid non-number types to Decimal type is not supported. Conversion from Numeric type to Decimal type is not supported. Conversion from Hexadecimal type is not supported. 4

5 Version Released March 2016 The following issues have been resolved in Amazon Redshift ODBC Driver Driver incorrectly sends SQL_BINARY, SQL_VARBINARY, and SQL_LONGVARBINARY bound parameters to the server. When using the driver in Microsoft Access, NUMERIC and TIMESTAMP data cause errors to occur. Version This issue has been resolved. The driver is now able to work with NUMERIC and TIMESTAMP data in Microsoft Access. Released November 2015 Enhancements & New Features HTTP proxies now supported You can now use the ProxyHost and ProxyPort options to configure the driver to connect to an HTTP proxy. SQL_DESC_UPDATABLE now reports the value SQL_ATTR_READWRITE for columns The driver has been updated to report columns as both readable and writable. Support added for using INSERT statements with the OPENQUERY syntax When the driver is working in "Use Multiple Statements" mode, you can now use INSERT statements with the OPENQUERY syntax. The following issues have been resolved in Amazon Redshift ODBC Driver Driver reports incorrect SQL_DIAG_ROWCOUNT value when using SQLGetDiagField. 5

6 The driver now reports the SQL_DIAG_ROWCOUNT value correctly. Driver reports incorrect CHAR_OCTET_LENGTH value when using SQLDescField or SQLColumns. The driver now reports the CHAR_OCTET_LENGTH value correctly. On Mac OS X, the driver version number does not display in the iodbc Data Source Chooser. The driver version number now displays as expected. When viewing metadata, the driver returns TIMESTAMPTZ instead of TIMESTAMP. TIMSTAMPTZ is not supported by Redshift. The driver now reports TIMESTAMP instead of TIMESTAMPTZ. Driver stops working during bulk fetches if some of the columns are not bound in the result set. You can now successfully run bulk fetches where some of the columns are not bound in the result set. When working with a table name that is longer than 64 characters, an error may occur. You can now work with table names that are longer than 64 characters. In some cases, when using a Linux host to connect to Redshift over a VPN, connection errors may occur. You can now successfully connect to Redshift over a VPN using a Linux host. When using the driver in Informatica PowerCenter, the driver fails to unload properly. You can now use the driver in Informatica PowerCenter without encountering issues during unloading. 6

7 Version Released May 2015 Enhancements & New Features Greatly improved performance when retrieving batches of rows The driver is now able to retrieve batches of rows much more quickly than in previous versions of the driver. Improved visibility of INFO messages Before, INFO messages generated by the server would only be written to the console. Now, those messages are exposed as ODBC warnings. Updated maximum length for catalog names The driver now reports that the maximum length of a catalog name is 64 instead of 0. This update improves the driver's compatibility with SAP applications. Support added for limiting result set size You can now specify a maximum size for the result sets that the driver returns by using the SQL_ATTR_MAX_ROWS statement attribute. The following issues were resolved in Amazon Redshift ODBC Driver When executing a query that uses a SQL_INTEGER parameter set to the minimum integer value, the driver returns an error. Before, executing a query with a SQL_INTEGER parameter set to the minimum value would cause the driver to return the following error message: "Conversion from number to string failed due to an undersized character buffer". The driver is now able to execute these queries correctly. Driver uses incorrect environment variable for looking up the global driver settings file. The environment variable that the driver uses to locate the amazon.redshiftodbc.ini configuration file has been renamed from REDSHIFTODBC to REDSHIFTODBCINI. 7

8 When using the driver in Tableau, tables cannot be displayed if they are contained by a schema that has a period (.) in the schema name. Tables are now displayed in Tableau as expected even when the schema name has a period (.). Driver stops working if Declare/Fetch mode is enabled and the server runs out of cursors. An improved response has been implemented for this issue. Now, when the driver is working in Declare/Fetch mode and the server runs out of cursors, the driver returns an error message instead of failing. When using the C# System.Odbc classes, inserting a non-english character as a parameter causes an error to occur. You can now insert non-english characters as parameters when using the C# System.Odbc classes without encountering any problems. 8

9 Contact Us For support, check the Amazon Redshift Forum at or open a support case using the AWS Support Center at 9