Previously, the default value was Disabled (0). The default value of the Bytea As LongVarBinary option (ByteaAsLongVarBinary connection property) is now Enabled (1). New default value for Bytea As LongVarBinary.
#AMAZON REDSHIFT ODBC DRIVER DRIVER#
Removed support for earlier versions of operating systemsīeginning with this release, the driver no longer supports the following operating systems: - Windows 7 SP1 - Windows Server 2008 R2 SP1 - SUSE Linux Enterprise Server (SLES) 11 - Debian 7 - Ubuntu 14.04įor a list of supported operating systems, see the Installation and Configuration Guide.For a list of supported Linux versions, see the Installation and Configuration Guide.ġ.4.18. Removed support for CentOS 6 and RHEL 6īeginning with this release, support for CentOS 6 and RHEL 6 have been removed.For more information, see the Installation and Configuration Guide. The connector's behavior for the query processing modes have been updated. Updated query processing modes behavior.The description of the EnforceSingleStatement and UseMultipleStatements options have been changed to reflect the actual behavior. Updated EnforceSingleStatement and UseMultipleStatements description.The following changes may disrupt established workflows for the connector.ġ.4.28. The connector does not support the use of negative values in timestamps. Timestamps do not accept negative values.The connector does not support parameterized procedure call queries if there is more than one procedures of different argument types that share the same name in the server. Known Issues The following are known issues that you may encounter due to limitations in the data source, the connector, or an application. When a query in a statement handle fails during SQLPrepare(), the connector incorrectly returns an "Error occurred while trying to run statement: a statement is already in progress" error message in another statement handle. When querying SQLSpecialColumns(), the connector returns the incorrect data type for the SCOPE column. When executing DDL and DML statements, the connector becomes unresponsive without closing the cursor or freeing the statement handle. When calling SQLEndTran() to complete a transaction and the server has terminated the connection, the connector incorrectly returns SQL_SUCCESS. The connector now uses an ORDER BY clause for these queries.
When Database Metadata Current Database Only is disabled and calling SQLTables with CatalogName set to SQL_ALL_CATALOGS, and SchemaName and TableName are empty strings, the connector returns query results tables in an incorrect order.Resolved Issues The following issues have been resolved in Simba Amazon Redshift ODBC Connector 1.4.32.
The release notes provide details of enhancements, features, known issues, and workflow changes in Simba Amazon Redshift ODBC Connector 1.4.32, as well as the version history.ġ.4.32 = = Magnitude Simba Amazon Redshift ODBC Data Connector Release Notes =
0 kommentar(er)
